SQL Server Performance Forum – Threads Archive
sql2k upgrade
hi, right now in process of upgrading from 7.0 to sql 2k.want to know where to make changes for sql 2k.
we are making list of all
stored procs
DTS packages
triggers
jobs
views. these are the changes on the server….
do i need to change anything else?? thank you
yamaha
Typically no need to change code in major terms, being similarity in functional aspects of SQL 7 to 2000 and if you perform upgrade it will let you if any issues or BACKUP/RESTORE 7 db to 2K it will be easy too. As always I recommend to refer to thishttp://www.sqlteam.com/item.asp?ItemID=9066 link for more information on upgrade. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
hi Satya, we want to make changes in SPs, triggers etc…listed are the chages we want to make… isNULLBased on SQL2000 standards when evaluating nulls you may no longer use equals (“=“) Double Quotes (“â€)In SQL 7, double quotes (“â€) could be used to delineate either strings or column names. In SQL 2000, double quotes can ONLY be used to delineate column names. Other strings MUST be delineated using single quotes (‘#%92). This is probably the most critical issue. Set ROWCOUNTThe SET ROWCOUNT setting for remote tables does not apply for INSERT statements. SQL 7 ignores the statement. This will result in a logical error. Reserved KeywordsSQL 2000 introduces three new reserved words: Collate, Function, and OpenXML. These words cannot be used to name tables, columns, stored procedures, or any other database objects. Doing so will result in a syntax error.
Server configuration optionsA number of database server configuration options are not supported in SQL 2000. do we have to modify all these……….also all the views and DTS packages??
yamaha
If database are included in updrade, via backup or attach, don’t forget to update statistics
Luis Martin …Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
Bertrand Russell
isNULL Based on SQL2000 standards when evaluating nulls you may no longer use equals (“=“)
As mentioned in the duplicate post no need to change any of the code. Double Quotes (“Ââ€) In SQL 7, double quotes (“Ââ€) could be used to delineate either strings or column names. In SQL 2000, double quotes can ONLY be used to delineate column names. Other strings MUST be delineated using single quotes (‘Â#%92). This is probably the most critical issue.
Where and when in the code you use? Set ROWCOUNT The SET ROWCOUNT setting for remote tables does not apply for INSERT statements. SQL 7 ignores the statement. This will result in a logical error.
Again where do you use this statement? Reserved Keywords SQL 2000 introduces three new reserved words: Collate, Function, and OpenXML
Yes its not good practice to created database objects with reserved keywords, if so try to change them before you upgrade. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
]]>