Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

SSIS – Transfer SQL Server Objects Debugged Expand / Collapse
Author
Message
Posted Wednesday, January 21, 2009 4:51 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, December 20, 2013 4:45 AM
Points: 236, Visits: 239
It is a real bug-bear how MS rely on users to do their debugging for them and as somebody pointed out, for free!
Actually, its at a cost to us having to pay for support and be able to log a call, for which they then accept as a bug!
Post #640570
Posted Monday, October 11, 2010 12:31 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 27, 2011 7:39 AM
Points: 4, Visits: 27
Excellent article...the communication is very clear. I have a similar problem with my database and have implemented a solution without using vb.net in which such procedures with changed names are found and filtered rather than being changed and compiled again in the destination database. I wonder if we can create a DDL trigger that can prevent users from changing names of Stored Procs from Object Explorer.
Post #1002397
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse