All geek questions in one place

SQL Server: how to determine what will break when overriding a database?

We are building a client application with the assumption that they will be upgraded to SQL Server 2005 with SQL Server 2000. We have completed our 2005 application and are ready to integrate. It turns out that they are not going to update their database server.

So now we are stuck trying to figure out what will break.

We do not have access to SQL Server 2000, so we can change the database compatibility to 80.

Apart from fully testing and verifying each stored procedure (and I read that changing the compatibility mode is not reliable), so testing will not be bombproof), is there any other way to determine what will break? Any tools out there? Scenarios?

Edit

I would rather not try to restore this on my production database server to see what errors are being spit out, so this is not a good option.

+3
source share
2 answers

Invite you to look at books on the Internet on a page that talks about the differences between them and look for these things. You can view the list and then search for new keywords in the table where the sp-text is stored. This will give you an initial list.

@rwmnau , SQL Server 2000 varchar (max) nvarchar (max), . SQl Server 2000 SSIS - SSIS , DTS.

, SQL Server 2000: http://www.microsoft.com/downloads/details.aspx?familyid=413744d1-a0bc-479f-bafa-e4b278eb9147&displaylang=en

, .

+4

, ANSI-SQL ( ), , , , , SQL 2000 ( , , ):

, , (, "sys" "sys." ) SQL 2000 2005+, d , :

SELECT *
  FROM syscomments --I know, using a sys table to figure it out :)
 WHERE text like '%sys%'

, , , , Microsoft SQL 2000 . ( ) - Microsoft , - , . ( , 2005 .), , .

+2

Source: https://habr.com/ru/post/1759153/

More articles:


All Articles