Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
NickStan
Starting Member
36 Posts |
Posted - 2009-10-22 : 11:08:44
|
Hi GuysI am having issues debugging the sql sent to the SQLStatementSource property in a Execute T-SQL Statement Task.The problem is I dont know how to see the statement that I have built so I cant debug it!I am getting file names from a table and looping around that recordset in a for each loop and then I set the SQLStatementSource property after I have built a (complicated) sql string.Any ideas on how to show the string built or show the full error message from SQL server because currently the error message from sql server is truncated?Many thanksNick |
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-10-23 : 03:58:24
|
You can always use the old MsgBox method :-)The full error message will be displayed in the error log (if you have enabled logging).And in development, the message will be in the Progress tab. Put the cursor over the error line, and right-click select "Copy Message Text" - paste in notepad to see full message. |
|
|
NickStan
Starting Member
36 Posts |
Posted - 2009-10-23 : 05:46:04
|
Yellowbug:Thanks for the advice - I can now see (all) of the error message! |
|
|
|
|
|