Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 Old Forums
 CLOSED - General SQL Server
 3 SQL servers suddenly can't write to db!!!
 Forum Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 09/26/2001 :  17:59:17  Show Profile  Visit AskSQLTeam's Homepage
Ricardo writes "We are running SQL server 6.5 on 3 win NT4 boxes. Box 1 is a live database, box 2 is a reporting database that contains the previous day's database, box 3 contains friday of the week before (training database).

On ALL databases, our front-end client CANNOT write to the database but CAN read to it. We're stumped, as the problem has occurred after 1 hour of this working day (logically, the training db is a copy from last week, therefore the whole thing should've been down for a whole week)

The front-end client hasn't changed, has been restored from backups, as has the main database. We can still read but not write on all 3 boxes. If you get in via ISQL_w, you CAN write. Both use OLE connections.

There are NO error messages on ANY of the boxes. There is plenty of diskspace on ALL boxes. The problem is repeated on all segments of the LAN and WAN. None of the NT permissions have changed. All boxes can be connected to via ISQL_w.

This is our mission critical app, and we're STUMPED!!!!"

Constraint Violating Yak Guru

455 Posts

Posted - 09/26/2001 :  18:05:07  Show Profile
Check to see if the database is read-only

Go to Top of Page


United Kingdom
12543 Posts

Posted - 09/30/2001 :  04:19:57  Show Profile  Visit nr's Homepage
How is the front end trying to write?
Via stored procs?
If so chack the user that is connected (from the server not what you expect it to connect as) and check permissions on that.

If via recordset methods then it is probably something to do with the setup that is now causing read only recordsets. Check the user again.

Maybe something in the network has changed to upset the connection or different version of mdac loaded somewhere.

Cursors are useful if you don't know sql.
You learn little from being right - benefit from being wrong.
Cold fizzy beer is wrong.
Go to Top of Page
  Previous Topic Topic Next Topic  
 Forum Locked
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.04 seconds. Powered By: Snitz Forums 2000