SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 ODBC Error 3157: Update to linked table failed
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

singhg8
Starting Member

United Kingdom
4 Posts

Posted - 01/29/2014 :  07:45:39  Show Profile  Reply with Quote
We have a SQL 2008 R2 standard edition installed on Server 2008. We use an access front-end which connects to a SQL backend tables which are linked with the app.

Since last 2 weeks, we are continuously getting application freeze with the error - ODBC Error 3157: Update to linked table "###" failed

So far I have done the below:

1. Added primary key to the table as it had an identity column only
2. Relinked all the table and redistributed the front-end to the users
3. Ensure SQL files are shrunk
4. Checked network connections connecting the server to the switch
5. Checked SQL configuration manager to ensure right accounts are being used for the SQL services

This issue is very sporadic and it is now becoming frustrating as it has been ongoing for couple of weeks.

Can anyone shed some light on this as I am running out of possible ideas.

singhg8

ahmeds08
Aged Yak Warrior

India
576 Posts

Posted - 01/29/2014 :  09:04:53  Show Profile  Send ahmeds08 a Yahoo! Message  Reply with Quote
Can you try this:
Open the database in design view.
Select Tools: Utilities: Linked Table Manager
Check the table you are having a problem with
Click the Ok Button
Since this is an ODBC link you may be prompted to select the appropriate
DSN. If you can identify it, then do so - otherwise cancel out.

Javeed Ahmed
Go to Top of Page

singhg8
Starting Member

United Kingdom
4 Posts

Posted - 01/29/2014 :  09:15:07  Show Profile  Reply with Quote
Thanks for your reply Javed. I have already tried this many times in last 2 weeks.

singhg8
Go to Top of Page

singhg8
Starting Member

United Kingdom
4 Posts

Posted - 01/29/2014 :  10:42:49  Show Profile  Reply with Quote
Hi All,

Is there anyone who can help with the issue please?

Thanks.

singhg8
Go to Top of Page

singhg8
Starting Member

United Kingdom
4 Posts

Posted - 01/31/2014 :  06:31:33  Show Profile  Reply with Quote
I have manged to resolve this issue. For all those people who are struggling to get an answer, please ensure that indexing has been properly set-up on resource hungry big SQL tables.

You can use SQL monitoring tools to analyse and find the long-running queries and then use SSMS (sql server management studio) feature called "Execution Plan" to create indexing. SSMS feature literally tells you what script to run if it finds that indexing of tableis required.

Hope this is useful to the needy people !!!


singhg8
Go to Top of Page

Bustaz Kool
Flowing Fount of Yak Knowledge

USA
1645 Posts

Posted - 01/31/2014 :  17:46:20  Show Profile  Reply with Quote
Be careful that you don't simply apply each index that is presented by SSMS. Usually, we look at the current set of indexes and compare it to the suggested index. Often there is a good deal of similarity and you can combine the two together.

===============================================================================
There are two kinds of light -- the glow that illuminates, and the glare that obscures. -James Thurber (1894-1961)
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000