December 12, 2007 at 7:09 am
We have a database release ever month for company website. The procedure for the release is to generate the scripts of the database objects and store it in the source safe. Then compare it with the previous saved scripts of last month and copy only the changed script. The database objects will be altered and created by many developers. I used to generate the database script in SQL Server 2000. There are around 400 tables and 450 procedures and the time taken for this is around 15-20 minutes maximum. Now we have upgraded to SQL SERVER 2005. Here to generate scripts I chose only create,Defaults,Drop and all the options in Table/View options. But the time taken by 2005 to generate scripts is very long. It takes more than 2 hours and this is affecting my release time.Why does the same script generation takes less time in 2000? Both are installed in the same server. When I checked the Generate script window I observed that generating the table script is the main time consuming rest all objects are very fast.
What can I do for this?
December 12, 2007 at 9:16 am
Are you able to run Profiler during script generation? It might give us some clues as to its cause - It's difficult otherwise!
Paul
December 12, 2007 at 10:07 am
I've noticed this too, with much frustration. I think the reason is because behind the scenes, the new Enterprise Manager uses SMO to generate scripts. At any rate, are you running SP2? I have noticed a slight increase in performance once that was installed.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply