|
|
You're in the
sql server odbc
group:SQL Server To Paradox
sql server odbc:
Hello, Is there anyone out there that has been able to successfully have SQL Server 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server 2000 and the Borland Database Engine v 5. We have been working with the Microsoft Paradox driver, with very poor results. We have had better luck with the Intersolv driver, but it is not 100%. Does anyone have a success story that uses these ODBC Driver or any other drivers. Please let me know.
Hi Brian,
The Microsoft Paradox driver should work just fine. Could you give us more details on what is going wrong with it? What exactly do you mean by "very poor results"? Jonathan [quoted text, click to view] Brian wrote:
> Hello, > > Is there anyone out there that has been able to successfully have SQL Server > 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server > 2000 and the Borland Database Engine v 5. > > We have been working with the Microsoft Paradox driver, with very poor > results. We have had better luck with the Intersolv driver, but it is not > 100%. > > Does anyone have a success story that uses these ODBC Driver or any other > drivers. Please let me know.
I would be glad to.
We are doing some further diagnostics on the SQL stuff now. But, there appears to be some limitations on the drivers ability to handle certain types of SQL code. For example here are some extracts from the ODBC log: sqlservr 1cc0-1c84 EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO) HDBC 05E218D8 HWND 00000000 WCHAR * 0x05CF7CF4 [ -3] "******\ 0" SWORD -3 WCHAR * 0x05CF7CF4 SWORD 2 SWORD * 0x00000000 UWORD 0 <SQL_DRIVER_NOPROMPT> DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0) DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0) Above appears to be a place to research why it seems slow slow. sqlservr 1cc0-1c84 EXIT SQLSetConnectAttrW with return code -1 (SQL_ERROR) SQLHDBC 05E218D8 SQLINTEGER 0 <SQL_ATTR_QUERY_TIMEOUT> SQLPOINTER 0x00000000 SQLINTEGER -6 DIAG [S1C00] [Microsoft][ODBC Paradox Driver]Optional feature not implemented (106) Above appears to be the driver is receiving code that it does not have the ability to support. System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 1 - I/O Error detected in read/write operation) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) We are also seeing a lot of the above error, and have not been able to resolve. This causes SQL Server to crash. Any ideas from anyone in regards to this would be greatly appreciated. [quoted text, click to view] "Jonathan Psaila-Depasquale" wrote:
> Hi Brian, > > The Microsoft Paradox driver should work just fine. Could you give us > more details on what is going wrong with it? What exactly do you mean > by "very poor results"? > > Jonathan > > > Brian wrote: > > Hello, > > > > Is there anyone out there that has been able to successfully have SQL Server > > 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server > > 2000 and the Borland Database Engine v 5. > > > > We have been working with the Microsoft Paradox driver, with very poor > > results. We have had better luck with the Intersolv driver, but it is not > > 100%. > > > > Does anyone have a success story that uses these ODBC Driver or any other > > drivers. Please let me know. > >
Additionally, if any has a list of commands or limitations the the driver can
support from SQL Server, it would be helpful for us to have. [quoted text, click to view] "Jonathan Psaila-Depasquale" wrote:
> Hi Brian, > > The Microsoft Paradox driver should work just fine. Could you give us > more details on what is going wrong with it? What exactly do you mean > by "very poor results"? > > Jonathan > > > Brian wrote: > > Hello, > > > > Is there anyone out there that has been able to successfully have SQL Server > > 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server > > 2000 and the Borland Database Engine v 5. > > > > We have been working with the Microsoft Paradox driver, with very poor > > results. We have had better luck with the Intersolv driver, but it is not > > 100%. > > > > Does anyone have a success story that uses these ODBC Driver or any other > > drivers. Please let me know. > >
Hi Brian,
I'll do some research into these errors. In the meantime have a quick browse through these articles to see if they talk about any of the functionality you have implemented and which is causing you problems - http://support.microsoft.com/search/default.aspx?catalog=LCID%3d1033&spid=global&query=Paradox&adv=&mode=s&cat=False&range=1-200. Furthermore, could you also tell me which version of MDAC and on what OS + SP? The best tool to check this with (and also do some minimal troubleshooting) is the MDAC component checker - http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en. Jonathan [quoted text, click to view] Brian wrote:
> I would be glad to. > > We are doing some further diagnostics on the SQL stuff now. But, there > appears to be some limitations on the drivers ability to handle certain types > of SQL code. For example here are some extracts from the ODBC log: > > > sqlservr 1cc0-1c84 EXIT SQLDriverConnectW with return code 1 > (SQL_SUCCESS_WITH_INFO) > HDBC 05E218D8 > HWND 00000000 > WCHAR * 0x05CF7CF4 [ -3] "******\ 0" > SWORD -3 > WCHAR * 0x05CF7CF4 > SWORD 2 > SWORD * 0x00000000 > UWORD 0 <SQL_DRIVER_NOPROMPT> > > DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr > failed (0) > > DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr > failed (0) > > Above appears to be a place to research why it seems slow slow. > > > sqlservr 1cc0-1c84 EXIT SQLSetConnectAttrW with return code -1 > (SQL_ERROR) > SQLHDBC 05E218D8 > SQLINTEGER 0 <SQL_ATTR_QUERY_TIMEOUT> > SQLPOINTER 0x00000000 > SQLINTEGER -6 > > DIAG [S1C00] [Microsoft][ODBC Paradox Driver]Optional feature not > implemented (106) > > Above appears to be the driver is receiving code that it does not have the > ability to support. > > System.Data.SqlClient.SqlException: A transport-level error has occurred > when receiving results from the server. (provider: Shared Memory Provider, > error: 1 - I/O Error detected in read/write operation) at > System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean > breakConnection) at > System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, > Boolean breakConnection) at > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject > stateObj) > > We are also seeing a lot of the above error, and have not been able to > resolve. This causes SQL Server to crash. > > Any ideas from anyone in regards to this would be greatly appreciated. > > "Jonathan Psaila-Depasquale" wrote: > >> Hi Brian, >> >> The Microsoft Paradox driver should work just fine. Could you give us >> more details on what is going wrong with it? What exactly do you mean >> by "very poor results"? >> >> Jonathan >> >> >> Brian wrote: >>> Hello, >>> >>> Is there anyone out there that has been able to successfully have SQL Server >>> 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server >>> 2000 and the Borland Database Engine v 5. >>> >>> We have been working with the Microsoft Paradox driver, with very poor >>> results. We have had better luck with the Intersolv driver, but it is not >>> 100%. >>> >>> Does anyone have a success story that uses these ODBC Driver or any other >>> drivers. Please let me know.
Regarding this error, there should be some more helpful errors in the
ERRORLOG of SQL Server. Could you copy and paste this log into a post please? System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 1 - I/O Error detected in read/write operation) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) What version, edition and SP of SQL Server are you running there? Jonathan [quoted text, click to view] Brian wrote:
> I would be glad to. > > We are doing some further diagnostics on the SQL stuff now. But, there > appears to be some limitations on the drivers ability to handle certain types > of SQL code. For example here are some extracts from the ODBC log: > > > sqlservr 1cc0-1c84 EXIT SQLDriverConnectW with return code 1 > (SQL_SUCCESS_WITH_INFO) > HDBC 05E218D8 > HWND 00000000 > WCHAR * 0x05CF7CF4 [ -3] "******\ 0" > SWORD -3 > WCHAR * 0x05CF7CF4 > SWORD 2 > SWORD * 0x00000000 > UWORD 0 <SQL_DRIVER_NOPROMPT> > > DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr > failed (0) > > DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr > failed (0) > > Above appears to be a place to research why it seems slow slow. > > > sqlservr 1cc0-1c84 EXIT SQLSetConnectAttrW with return code -1 > (SQL_ERROR) > SQLHDBC 05E218D8 > SQLINTEGER 0 <SQL_ATTR_QUERY_TIMEOUT> > SQLPOINTER 0x00000000 > SQLINTEGER -6 > > DIAG [S1C00] [Microsoft][ODBC Paradox Driver]Optional feature not > implemented (106) > > Above appears to be the driver is receiving code that it does not have the > ability to support. > > System.Data.SqlClient.SqlException: A transport-level error has occurred > when receiving results from the server. (provider: Shared Memory Provider, > error: 1 - I/O Error detected in read/write operation) at > System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean > breakConnection) at > System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, > Boolean breakConnection) at > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject > stateObj) > > We are also seeing a lot of the above error, and have not been able to > resolve. This causes SQL Server to crash. > > Any ideas from anyone in regards to this would be greatly appreciated. > > "Jonathan Psaila-Depasquale" wrote: > >> Hi Brian, >> >> The Microsoft Paradox driver should work just fine. Could you give us >> more details on what is going wrong with it? What exactly do you mean >> by "very poor results"? >> >> Jonathan >> >> >> Brian wrote: >>> Hello, >>> >>> Is there anyone out there that has been able to successfully have SQL Server >>> 2000 talk to Paradox databases, by using an ODBC Driver between SQL Server >>> 2000 and the Borland Database Engine v 5. >>> >>> We have been working with the Microsoft Paradox driver, with very poor >>> results. We have had better luck with the Intersolv driver, but it is not >>> 100%. >>> >>> Does anyone have a success story that uses these ODBC Driver or any other >>> drivers. Please let me know.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |