By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,363 Members | 2,417 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,363 IT Pros & Developers. It's quick & easy.

SQL Server 2005 ODBC Logging Problems

P: 1
Hi All,
I am working with a software package that logs messages via ODBC to a remote SQL Server 2005 Service Pack 2 database. The server OS is Server 2003 Service Pack 1. The software that we are working with successfully creates the SQL table and SQL user for the logging as the ODBC connection is set up. We have verified that both the user and the table have been set up on the SQL Server machine. By default, full permissions are not granted to the user associated with the table. We went into SQL and granted full table permissions to this user. It seems as though everything should work, but we aren't seeing any data in the table. We ran an ODBC trace and received the following message:

DIAG [S0001] [Microsoft][ODBC SQL Server Driver][SQL Server]There is already an object named 'TableName' in the database. (2714)

The table is already created in SQL 2005. I'm not sure why it would try to create the table again if it already exists??? There is no indication that the software is trying to create the table again. We have used this software with SQL 2000 and have not experienced this issue.

Are there any known issues with ODBC logging to a SQL Server 2005 database? Could this be an authentication or security issue? I haven't worked extensively with SQL Server 2005, but have worked with SQL Server 2000 quite a bit. I just don't know if there is something that we are missing in the configuration within SQL Server 2005. Any assistance is appreciated. Thanks!
Mar 20 '08 #1
Share this Question
Share on Google+
1 Reply


ck9663
Expert 2.5K+
P: 2,878
Hi All,
I am working with a software package that logs messages via ODBC to a remote SQL Server 2005 Service Pack 2 database. The server OS is Server 2003 Service Pack 1. The software that we are working with successfully creates the SQL table and SQL user for the logging as the ODBC connection is set up. We have verified that both the user and the table have been set up on the SQL Server machine. By default, full permissions are not granted to the user associated with the table. We went into SQL and granted full table permissions to this user. It seems as though everything should work, but we aren't seeing any data in the table. We ran an ODBC trace and received the following message:

DIAG [S0001] [Microsoft][ODBC SQL Server Driver][SQL Server]There is already an object named 'TableName' in the database. (2714)

The table is already created in SQL 2005. I'm not sure why it would try to create the table again if it already exists??? There is no indication that the software is trying to create the table again. We have used this software with SQL 2000 and have not experienced this issue.

Are there any known issues with ODBC logging to a SQL Server 2005 database? Could this be an authentication or security issue? I haven't worked extensively with SQL Server 2005, but have worked with SQL Server 2000 quite a bit. I just don't know if there is something that we are missing in the configuration within SQL Server 2005. Any assistance is appreciated. Thanks!

"The software that we are working with successfully creates the SQL table and SQL user for the logging as the ODBC connection is set up." This tells me that whenever a connection is successfully done, it will create the table. Hence, the error. If you can modify your apps, try to check for existence of the table first then do the necessary step (to rename or drop) before proceeding with creation.

-- CK
Mar 20 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.