Re: SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic
From: Jacco Schalkwijk (NOSPAMjaccos_at_eurostop.co.uk)
Date: 02/20/04
- Next message: Stephen: "Re: STORED PROCEDURE"
- Previous message: Alexis M: "Stored proc issue... Best parameter type to use?"
- In reply to: glennf: "SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic"
- Next in thread: Erland Sommarskog: "Re: SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Feb 2004 14:10:26 -0000
SQL Server Best Practises Analyzer can help you quite a bit with this,
although it isn't specific for 6.5 to 2000 conversions:
http://www.microsoft.com/downloads/details.aspx?FamilyId=B352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en
(free download)
-- Jacco Schalkwijk SQL Server MVP "glennf" <gfroemming@yahoo.com> wrote in message news:A1791EA7-2B8A-4639-9EE9-73617E22FC3E@microsoft.com... > SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic > > Are there any tools for locating potentially problematic (Syntactic or sematic) SQL code (in stored procs, triggers, SQL statements in apps, views, ...)? Note that this tool would for the SQL code, not the Server upgrade, ie not the upgrade wizard, which I believe upgrades only the server infrastructure. For example, in 6.5 a zero length string is reported as NULL. I'm looking for a tool that would simply highlight obvious (Syntactic) and subtle(semantic) differences for review, similar to what "Lint" does for C based languages. > >
- Next message: Stephen: "Re: STORED PROCEDURE"
- Previous message: Alexis M: "Stored proc issue... Best parameter type to use?"
- In reply to: glennf: "SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic"
- Next in thread: Erland Sommarskog: "Re: SQL 6.5=>2000 Upgrade: ?Lint like tool for identifying potentially problematic"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
