[freetds] MS SQL Server Lockup
brian.bruns at gmail.com
Tue Sep 27 15:54:51 EDT 2005
I'm more of a sybase guy, but here goes.
It sounds like what you have are locks being held open. You can see
this by doing an sp_who on the sql server and there should be
something in the "blocked" column. That something will be the spid of
the blocking process.
You can track this back (look at the spid shown and follow that one's
blocked column until you find one with '0', and that'll be the process
holding the original lock). You can look at the spid causing this and
see where comes from (i think you can still do a "select * from
master..sysprocesses" in sql server to get the columns that don't show
up on sp_who, but i'm sure someone here will correct me if not).
Anyway, figure out what that is and then you can "kill <spid>" to get
rid of it and it's locks to eliminate the immediate problem, but
you'll need to look deeper to see what causes it.
2005/9/27, RCM2, Inc <rcm2 at rmcshane.com>:
> We are running a Web management package (written in Perl) under Apache on
> Lunux. We are using FreeTDS to connect to a Microsoft SQL 2000 Server. The
> connect string is dbi:Sybase:server=wbshost;database=testdb
> If we stop and start Apache on the Linux box, the SQL server will lockup; it
> will still do selects, but will not do any updates.
> We use TDS in other applications and the only unique thing we see is that in
> the web content management application the connection is kept open; in most
> of our other applications, the connection is opened, some work done and the
> connection closed.
> Any ideals would be appreciated. This connection is to a live production
> box, so bringing down the SQL box is not well received.
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
More information about the FreeTDS