Hello Mikewo
Thanks for posting this question.
We are aware of the misleading description, which is an error. The descriptiong will be fixed in our future release.
Unfortunately, the ability to generate drop followed by create is not supported by the Wizard. The work around is to first generated drop scripts & then generate create scripts.
Thank you,
[Venkat]
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for the reply Venkat. I think I will miss the ability to do the drop and create in the same script generation. Enterprise Manager's script wizard could do this. Hopefully some update in the future will put this ability back into the product.
Mikewo|||Yes, thank you for the reply.
I too would enjoy seeing that functionality back, 2 passes to accomplish 1 thing is monotonous.|||
Venkat,
And how long will we have to wait for this simplest and most useful option? I hope it will be available as a Global option, not on a database by database basis as it is now.
|||
In my opinion this is a bug. Obviously, based on the description the functionality was expected, and it is not provided.
Terry
|||I've reported it as a bug since IMHO it is one (not working as documented). Title is:
Script Behavior in Script Wizard does not allow 3rd option
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=605eb110-2335-4275-b440-5d299c484ebf
Add your vote on it if you think it is important to you.
|||Does that mean you will be bringing back the Crop followed by Create, or leaving it out? This is a very useful feature!|||
We consider it a bug, and we would appreciate the ability to create a drop and create statement in one pass. Additionally, it would be very useful to script ALL databases, logins, users and roles in one pass.
Kind regards
Titus
|||It seems to make perfect sense that the wizard SHOULD support the Drop/Create scenario. It's even a bit ridiculous that it doesn't! 2005 seems to be a step backward as far as the scripting wizard goes.|||VenkatKrish wrote: Hello Mikewo Thanks for posting this question.
We are aware of the misleading description, which is an error. The descriptiong will be fixed in our future release.
Unfortunately, the ability to generate drop followed by create is not supported by the Wizard. The work around is to first generated drop scripts & then generate create scripts.
Thank you,
[Venkat]
This posting is provided "AS IS" with no warranties, and confers no rights.
Dear Venkat:
Thanks for the clarification. THE BUG IS NOT IN THE DESCRIPTION, THE BUG IS IN THE FUNCTIONALITY! When I push a revised batch of stored procedures to the production server, I can do it with the server on-line with scripts done via drop/create. I then have a small window of time that the system might claim a stored procedure is not present. This window is small enough to risk doing while users are in the database. This is not true if I have to do every updated SP as a mass of drops followed by a mass of creates. Then I have to take the applications off-line.
Please give us back the functionality we had soon!
No comments:
Post a Comment