generating database scripts - VERY SLOW

[johnl]

Has anybody else experienced how long it takes to generate scripts from
Management Studio? I'm launching the wizard (right click database/ tasks /
generate scripts). The wizard takes me through a couple of screen to set my
options. I finally get to the window where it's processing the objects.
After 10 minutes, only 3 objects have been completed. A database with
hundreds of tables and views will take hours.

Is there any way to speed this up? Right clicking on a table or view and
generating the DDL for that one object only takes a few seconds.

It was never this slow in SQL Server 2000.

[Aaron Bertrand [SQL Server MVP]]

The original release of SSMS was, yes, very slow. I think it is a bit
better in more recent builds, have you applied SP2 to your client tools?

Post by johnl
Has anybody else experienced how long it takes to generate scripts from
Management Studio? I'm launching the wizard (right click database/ tasks /
generate scripts). The wizard takes me through a couple of screen to set my
options. I finally get to the window where it's processing the objects.
After 10 minutes, only 3 objects have been completed. A database with
hundreds of tables and views will take hours.
Is there any way to speed this up? Right clicking on a table or view and
generating the DDL for that one object only takes a few seconds.
It was never this slow in SQL Server 2000.

[johnl]

Not sure what version I'm at, don't know if this is SP2 or not?

Microsoft SQL Server Management Studio 9.00.3042.00

[Tom Cooper]

That's SP2.

You can always find the service pack level by running

Select ServerProperty('ProductLevel')

Tom

Post by johnl
Not sure what version I'm at, don't know if this is SP2 or not?
Microsoft SQL Server Management Studio 9.00.3042.00

[Aaron Bertrand [SQL Server]]

Post by Tom Cooper
That's SP2.
You can always find the service pack level by running
Select ServerProperty('ProductLevel')

(But that doesn't tell you the version of client tools...)

[Tom Cooper]

True. Thanks for catching that.

Post by Aaron Bertrand [SQL Server]

Post by Tom Cooper
That's SP2.
You can always find the service pack level by running
Select ServerProperty('ProductLevel')

(But that doesn't tell you the version of client tools...)

[Aaron Bertrand [SQL Server]]

Several connect items I have reviewed seem to indicate that Microsoft thinks
they have solved this problem (or in a couple of cases, they mention some of
the issues brought up in the item, but not the speed). It is unclear after
reading them all whether they think they have fixed this in SP2 or the
typically vague "future release(s)"...

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=259838

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125313

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=228719

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126912

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=259838

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262072

There are probably others; I did not perform an exhaustive search. Just
wanted to show you that you are not alone, and that some in Redmond seem to
think that it is fixed. :-)

Post by johnl
Not sure what version I'm at, don't know if this is SP2 or not?
Microsoft SQL Server Management Studio 9.00.3042.00