Instead of dropping the scripts on the destination server, why no use ALTER PROC instead. You can have the SQL Server 2000 Query Analyser create the ALTER scripts for you (and it seems to keep most of the formatting, some spaces/tabs seem to get switched around, but that's it)
Cheers Ken ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From: "Anders Lundholm" <[EMAIL PROTECTED]> Subject: Re: Preserving SQL formatting with SQL MMC object transfer : Hello! : : Come on. Could it really be, that nobody on this list knows how to fix this : problem?! : : > This problem related to SQL Server 2000 (and possible 7.0). : > : > The problem is quite simple actually - I'm loosing my formatting in stored : > procedures, triggers and so on when using the SQL MMC (Management Console) : > to object-transfer a database from one server to the other (when including : > tables, stored procedures etc. in the transfer). : > : > My comments and indents are preserved, but any additional linebreaks in : the : > code are simply truncated. It makes the code look really untidy and hard : to : > overlook. : > : > I am quite good at keeping my triggers and stored procedures tidy with : e.g. : > linebreaks, comments and indents, so you can probably imagine how annoying : > this is. It's of great importance to me (it's easy, I like my code to be : > clean when another programmer is looking t it). : > : > The current solution is drop all stored procedures on the destination : server : > and re-create them with a seperate generated script. When using the : > "Generate SQL Script" feature from within the SQL MMC. : > : > I am desperate and am hoping that someone could cast some light in my : > darkness .. MSDN, Google and Books Online didn't provide me with any clues : > at all. : > : > Thanks in advance. --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
