Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts

Thursday, March 8, 2012

Database restore failed w/ConnectionRead (WrapperRead()) error

User attempts to restore database and receives the following error:
Title Bar:
Microsoft SQL-DMO (ODBC SQLState: 01000)
Error:
ConnectionRead (WrapperRead())
General network error. Check your network documentation.
Processed 1 pages for database 'xxxx', file 'xxxx' on file 1.
Once the user clicks past the errors and refreshes their databases,
the database does show up in the list and it was successfully
restored.Hello
Could you please send the SQL errorlog from the time that this failure
occured.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Sunday, February 19, 2012

database question

I have an Access application that links to SQL Server tables via an ODBC link.

I execute the following query in the Access application,

SELECT customerName From customers Where stateCode = 'CA'

My question:

Who (Access, SQL Server or the ODBC provider) selects based on the state code?

Does SQL Server only return customerNames where stateCode = 'CA'
OR
Does SQL Server return ALL rows and let Access select the customerNames where stateCode = 'CA'
OR
Does SQL Server return ALL rows and let the ODBC provider select and return only the appropriate rows to Access?

Thanks for your helpThe cleanest way to determine this is to run the query while SQL Profiler is running, and see what gets passed to SQL Server. My guess is that Access only asks for the rows where stateCode is CA.|||Agree with D.R. However, from what I remember it depends on the ODBC driver. If the remote server (in this case SQL) implements a specific part of the ODBC capabiliies then it will do the query on the server, otherwise the client has to do it. I'm pretty sure SQL will implement that capability.