|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, June 15, 2012 6:47 PM
Points: 8,
Visits: 36
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Tuesday, April 19, 2011 5:10 PM
Points: 275,
Visits: 168
|
|
Thanks Steve, this was helpful that you debugged this down to the internal sql code.
Karen Gayda MCP, MCSD, MCDBA
gaydaware.com
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:43 AM
Points: 582,
Visits: 1,601
|
|
| Refreshingly well written article....but this 'issue' has been present for a very long time (long before SSIS) in Enterprise Manager. You can fall victim to its consequences, no matter how you script your database.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 6:30 AM
Points: 562,
Visits: 1,404
|
|
Hate to think how much coffee and hair pulling it took to weed this out
------------------------------------------------------------------------- Normal chaos will be resumed as soon as possible.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, August 05, 2010 1:47 AM
Points: 3,
Visits: 10
|
|
There are a lot of other erros in this task. Microsoft told us, they will be corrected maybe in SQL2k8. thank you Microsoft!! Very helpful
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, August 11, 2010 9:16 AM
Points: 8,
Visits: 46
|
|
GREAT debugging & documentation! I've seen this happen before in my databases and did narrow it down to renaming. I just try not to rename things in Management Studio anymore. From experience, I found it's more reliable to DROP & CREATE again. Did you submit this bug to Microsoft?
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, August 05, 2010 1:47 AM
Points: 3,
Visits: 10
|
|
| Yes, as a premier support customer we opened 2 Calls. They know the error but they won't change it in the next time.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, February 09, 2009 5:26 PM
Points: 1,
Visits: 28
|
|
I've found that this is not the only task that has execution errors. I recently received SSIS training as well, and from a DBA perspective, everything worked great in class. When I got back to the office, the problems began. Specifically, the copy database task and the transfer login tasks did not do what they were supposed to do. I'll post more information when I get the time to gather the results. Cheers!
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Monday, February 18, 2013 10:46 AM
Points: 226,
Visits: 126
|
|
| A closely related issue exists with the sp_rename stored proc in SQL 2000. If you use sp_rename to rename a view (which Enterprise Manager and Management Studio seem to do under the covers), the view still retains its old name in syscomments. Scripting that view to a file (using Management Studio or Enterprise Manager) and then running the resulting script file will create the view with its OLD name.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: 2 days ago @ 2:19 PM
Points: 30,
Visits: 236
|
|
caveat: Good luck changing a system table in 2005
|
|
|
|