problem w/first SQL Server 2005 customer... 1

[jacktek]

Our software runs on SQL Server 2000. One of the stored procedures executes sp_rename to rename columns in a table.
When running the sproc in Query Analyzer the message appears "3604 - Caution: Changing any part of an object name could break scripts and stored procedures."
When the VB6 apps execute this sproc there is no problem whatsoever.
However, we have a client who is using SQL Server 2005. On their system (same databases, same VB6 apps, just SQL Server 2005 instead of 2000), the VB6 app blows up, with the same error message as above.
Is there a way to modify the script so that it can trap the above "3604 - Caution: --" message and not send it up to the app ? Or a setting to change so that SQL Server 2005 will not send up "cautions" as "errors" ???

Thanks

 

[ilyad]

Check ANSI_WARNINGS in BOL

 

[ilyad]

Seems like it doesn't if this link is recent

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=266048

 

[mrdenny]

There are several changes in SQL 2005 in the way that text output from stored procedures is sent back to the client application. This is among one of them.

Did anyone tell your client that it is certified to work on SQL 2005? If you didn't I'd recommend telling them that they need to downgrade to SQL 2000 and use the app until you have certified your app on SQL 2005.

If you check the VB6 app you may notice that an extra recordset is now being returned. That recordset probably has the text from the caution message in it.

I do know that print statements are returned back differently in SQL 2005 than they were in SQL 2000.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[jacktek]

I have just changed the app (VB6 program) to ignore the particular "error" - in error handling just saying "if err.number = xxx and err.description = xxx then resume next".
Thanks everyone for the helpful posts.

 

[mrdenny]

no problem.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com