469,287 Members | 2,436 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,287 developers. It's quick & easy.

SQL Server 2005 ODBC Logging Problems

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
1 1405
ck9663
2,878 Expert 2GB
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.

Similar topics

1 post views Thread by chloe.crowder | last post: by
10 posts views Thread by MVChauhan | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.