Re: SQL Native Client vs SQLOLEDB

The fix is to always owner (or in 2005 schema) qualify all references to database objects regardless of it is dbo or something else. This is especially true for executing stored procedures. I have not experienced this issue so I can't say if this is a bug or if it will be fixed. But I do know that you should fix the app to do the correct thing and you won't have these issues or others that may be caused by not qualifying the sps.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"RichardO" <RichardO@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:23CB6B99-4CA4-4074-B650-8666772CDFC3@xxxxxxxxxxxxxxxx
I work with Powerbuilder. SNC client has better performance than SQLOLEDB
when running Powerbuilder against SQL Server 2000. However, we found out that
SNC client requires that some stored procedures have the dbo prefix or else
the call the stored procedure fails. When connected to SQLOLEDB there is no
problem. We are using the latest SNC client. Would this problem be fixed in
SNC client in the future? How do I get around this problem using SNC

.

Loading