September 28, 2008 at 10:57 pm
Hello,
I have a Heat SQL 2000 database which has has some SP and triggers written for it. The customer now wants to move the database onto an SQL 2005 server and change the authentication over to windows from SQL authentication.
The Heat program has a load DB utility, which will move the heat tables. I was thinking if a did a copy of the database either through backup and restore or through a move would this keep the database entact and make it 2005 compatibile? Or should i recreate all the triggers and SP again in sql 2005 Once I have used the program load database utility, to move it onto 2005 which i think is more long winded?
I hope my question makes sense, I guess in simple terms does a move or copy database from 2000 to 2005 bring across all the stored procedures and triggers that were created for that database or is there a better way to move across to 2005 and is there anything I should be wary of? I am hoping the move or copy will do the trick and I do not have to recreate the SP or triggers again..
Thank you
Una
September 29, 2008 at 12:04 am
I do not know about the HEAT program but a backup/restore or a move will keep the stored procs and triggers. You will not have to re-create them.
How ever its a good idea to run the database upgrade advisor
before upgrading your db to sql 2005. It will point out issues if any.
If you are planning to use SQL 2005 features in your db make sure to set the compatibility of your db to 90 after your upgradation is over.
Also check out the web, there are many article on this subject.
"Keep Trying"
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply