HELP! sp or other tool to help diagnose recent record deletion?

I'm trying to trouble shoot an app that after two years of running
more or less fine has suddenly had a problem. An average user was
filling out a web form and clicked save, only to have their entire
multi page report form get obliterated. This user has no delete
rights, and even if they had pressed cancel the ASP page would simply
not write that page...but would not delete the entire series of
records.
I am stepping through ASP code and trying to recreate the problem but
I'm relatively new to SQL and not sure what sytem stored procedures or
functions might help me...records of recent deletes (within the last
few hours), userinfo (who really deleted the record)? Etc.
Coincidentally (perhaps) this server was nearly full (aprox 700 megs
left). I know...this is terrible. I've been harping my sysadmin to get
some non DB related stuff off my SQL server and we cleared a few Gigs
off this morning! Anyway, it's very likely the cause...again...could
someone point me to what logs or functions or documentation I should
be looking at that might help me verify this?
Many thanks!!
This might help you -- these guys have some good tools. I recommend,
though, that you restore the database to another area on the server and
compare the data with some custom queries to see what's missing...
http://www.red-gate.com/products/SQL_Log_Rescue/index.htm?gclid=CK-roqn2mIoCFRyVFQodbFaonQ
mahalie@.gmail.com wrote:
> I'm trying to trouble shoot an app that after two years of running
> more or less fine has suddenly had a problem. An average user was
> filling out a web form and clicked save, only to have their entire
> multi page report form get obliterated. This user has no delete
> rights, and even if they had pressed cancel the ASP page would simply
> not write that page...but would not delete the entire series of
> records.
> I am stepping through ASP code and trying to recreate the problem but
> I'm relatively new to SQL and not sure what sytem stored procedures or
> functions might help me...records of recent deletes (within the last
> few hours), userinfo (who really deleted the record)? Etc.
> Coincidentally (perhaps) this server was nearly full (aprox 700 megs
> left). I know...this is terrible. I've been harping my sysadmin to get
> some non DB related stuff off my SQL server and we cleared a few Gigs
> off this morning! Anyway, it's very likely the cause...again...could
> someone point me to what logs or functions or documentation I should
> be looking at that might help me verify this?
> Many thanks!!
>
-Dave Markle
http://www.markleconsulting.com/blog
sql

HELP! sp or other tool to help diagnose recent record deletion?

I'm trying to trouble shoot an app that after two years of running
more or less fine has suddenly had a problem. An average user was
filling out a web form and clicked save, only to have their entire
multi page report form get obliterated. This user has no delete
rights, and even if they had pressed cancel the ASP page would simply
not write that page...but would not delete the entire series of
records.
I am stepping through ASP code and trying to recreate the problem but
I'm relatively new to SQL and not sure what sytem stored procedures or
functions might help me...records of recent deletes (within the last
few hours), userinfo (who really deleted the record)? Etc.
Coincidentally (perhaps) this server was nearly full (aprox 700 megs
left). I know...this is terrible. I've been harping my sysadmin to get
some non DB related stuff off my SQL server and we cleared a few Gigs
off this morning! Anyway, it's very likely the cause...again...could
someone point me to what logs or functions or documentation I should
be looking at that might help me verify this?
Many thanks!!This might help you -- these guys have some good tools. I recommend,
though, that you restore the database to another area on the server and
compare the data with some custom queries to see what's missing...
http://www.red-gate.com/products/SQL_Log_Rescue/index.htm?gclid=CK-roqn2mIoCFRyVFQodbFaonQ
mahalie@.gmail.com wrote:
> I'm trying to trouble shoot an app that after two years of running
> more or less fine has suddenly had a problem. An average user was
> filling out a web form and clicked save, only to have their entire
> multi page report form get obliterated. This user has no delete
> rights, and even if they had pressed cancel the ASP page would simply
> not write that page...but would not delete the entire series of
> records.
> I am stepping through ASP code and trying to recreate the problem but
> I'm relatively new to SQL and not sure what sytem stored procedures or
> functions might help me...records of recent deletes (within the last
> few hours), userinfo (who really deleted the record)? Etc.
> Coincidentally (perhaps) this server was nearly full (aprox 700 megs
> left). I know...this is terrible. I've been harping my sysadmin to get
> some non DB related stuff off my SQL server and we cleared a few Gigs
> off this morning! Anyway, it's very likely the cause...again...could
> someone point me to what logs or functions or documentation I should
> be looking at that might help me verify this?
> Many thanks!!
>
-Dave Markle
http://www.markleconsulting.com/blog

HELP! sp or other tool to help diagnose recent record deletion?

I'm trying to trouble shoot an app that after two years of running
more or less fine has suddenly had a problem. An average user was
filling out a web form and clicked save, only to have their entire
multi page report form get obliterated. This user has no delete
rights, and even if they had pressed cancel the ASP page would simply
not write that page...but would not delete the entire series of
records.
I am stepping through ASP code and trying to recreate the problem but
I'm relatively new to SQL and not sure what sytem stored procedures or
functions might help me...records of recent deletes (within the last
few hours), userinfo (who really deleted the record)? Etc.
Coincidentally (perhaps) this server was nearly full (aprox 700 megs
left). I know...this is terrible. I've been harping my sysadmin to get
some non DB related stuff off my SQL server and we cleared a few Gigs
off this morning! Anyway, it's very likely the cause...again...could
someone point me to what logs or functions or documentation I should
be looking at that might help me verify this?
Many thanks!!This might help you -- these guys have some good tools. I recommend,
though, that you restore the database to another area on the server and
compare the data with some custom queries to see what's missing...
http://www.red-gate.com/products/SQ...br />
odbFaonQ
mahalie@.gmail.com wrote:
> I'm trying to trouble shoot an app that after two years of running
> more or less fine has suddenly had a problem. An average user was
> filling out a web form and clicked save, only to have their entire
> multi page report form get obliterated. This user has no delete
> rights, and even if they had pressed cancel the ASP page would simply
> not write that page...but would not delete the entire series of
> records.
> I am stepping through ASP code and trying to recreate the problem but
> I'm relatively new to SQL and not sure what sytem stored procedures or
> functions might help me...records of recent deletes (within the last
> few hours), userinfo (who really deleted the record)? Etc.
> Coincidentally (perhaps) this server was nearly full (aprox 700 megs
> left). I know...this is terrible. I've been harping my sysadmin to get
> some non DB related stuff off my SQL server and we cleared a few Gigs
> off this morning! Anyway, it's very likely the cause...again...could
> someone point me to what logs or functions or documentation I should
> be looking at that might help me verify this?
> Many thanks!!
>
-Dave Markle
http://www.markleconsulting.com/blog

Help! Db-library network communications layer not loaded.

Hi,
We are using a windows application that uses MSDE 2000 on an XP Pro Machine
as a server.
Everthing was fine until last Friday. Suddenly, the XP server computer
started to give this error "Db-library network communications layer not
loaded." when we started to run application on it.
From other client computers we can succesfully connect and run the
application, but somehow the main machine does not work. I thought the
automatic update was on and it updated some MDAC drivers or may be Net
framework. I tried to install MDAC 2.7, but still no change. (I tired some
web searches but still nothing)
I really appreciate if you can give any suggestions/solutions.
Thanks.
Onur Baser
DB-Library is not part of MDAC or MSDE, so probably you had it on your other
machine because you installed the client tools or something.
Anyhow I also hope you realize that DB-Library is a dead API since the
introduction of SQL Server 7.0 in 1998 and it does not allow you to connect
to named instances for example (without using an alias or protocol prefix),
Unicode, strings longer then 255 or any of the other new data types
introduced in SQL Server 7.0 or 2000.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Onur Baser" <onur@.baserler.com> wrote in message
news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are using a windows application that uses MSDE 2000 on an XP Pro
> Machine as a server.
> Everthing was fine until last Friday. Suddenly, the XP server computer
> started to give this error "Db-library network communications layer not
> loaded." when we started to run application on it.
> From other client computers we can succesfully connect and run the
> application, but somehow the main machine does not work. I thought the
> automatic update was on and it updated some MDAC drivers or may be Net
> framework. I tried to install MDAC 2.7, but still no change. (I tired some
> web searches but still nothing)
> I really appreciate if you can give any suggestions/solutions.
> Thanks.
> Onur Baser
>
|||Thank you,
I will see what I can do, but is really wierd that it just happened.
Best Regards,
OnuR
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:uLSRUJWlEHA.3432@.TK2MSFTNGP14.phx.gbl...
> DB-Library is not part of MDAC or MSDE, so probably you had it on your
> other machine because you installed the client tools or something.
> Anyhow I also hope you realize that DB-Library is a dead API since the
> introduction of SQL Server 7.0 in 1998 and it does not allow you to
> connect to named instances for example (without using an alias or protocol
> prefix), Unicode, strings longer then 255 or any of the other new data
> types introduced in SQL Server 7.0 or 2000.
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Onur Baser" <onur@.baserler.com> wrote in message
> news:u18HnHVlEHA.596@.TK2MSFTNGP11.phx.gbl...
>

HELP! ODBC becoming unusable

Here goes: We have situation at a customer site where users are suddenly unable to connect to SQL 2K via ASP using ODBC via DSN. While the customer is in this state, our Windows clients, which connect using OLE DB (ADO) to the same DB as the ASP, seem to be connecting without problems. Therefore, the problem seems to be with ODBC.

Additional details about the problem site:
SQL ODBC 3.50
Win2K Server SP 4.
SQL2k SP2.
MDAC 2.62
<100 users total
Moderate usage of our ASP interface

Note: SQL2k and IIS are on the same LAN-side server.

FYI: Another part of the problem is that I'm a developer and am not that familiar with the tools available to help me troubleshoot this kind of problem.

We've tried using Perfmon to monitor connection pooling, but nothing stood-out.

We've tried using netstat (with various switches), but nothing stood-out.

Does anybody have any advice?At least apply SP3 to your SQL.|||http://www.winnetmag.com/Windows/Article/ArticleID/3507/3507.html and take help of ODBC trace.
Check this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;268591 and corresponding referenced KBAs to take help of ODBC tracing to troubleshoot the problem.

Ensure both client and server are enabled with similar protocol, service packs as referred.|||Originally posted by rdjabarov
At least apply SP3 to your SQL.

Thanks. We will be advising them to update SQL to SP3, but it's not very comforting to us to give what they'll perceive as a solution, when we heavn't even identified the problem.|||While many of us here know client connectivity, it's still a SQL Server forum, not SQL Client ;)

I'd follow Satya's suggestions, at least you can see for yourself if you're even getting to the server.|||Originally posted by Satya
http://www.winnetmag.com/Windows/Article/ArticleID/3507/3507.html and take help of ODBC trace.
Check this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;268591 and corresponding referenced KBAs to take help of ODBC tracing to troubleshoot the problem.

Ensure both client and server are enabled with similar protocol, service packs as referred.
That's some great information! But won't this only trace activity across an open connection (implicit or explicit)? If so, I'm not sure it'll help because the problems is that at some point, the ASP are simply unable to connect via DSN using ODBC.

Given that it's as though SQL is simply inaccessable via the DSN, even when the ADO OLE DB client app is connecting fine, we've been speculating (with help from Microsoft) that the problem is with ODBC's connection pooling. We've tried to set-up performance logging of connection pooling in-house in an effort to determine it's potential usefulness to our scenario in production, but our in-house graphs show no activity...probably due to the relatively low activity in our development environment. We walked the customer through setting it up on their server anyhow.

Just recently, the problem occurred again on the customer's server. Before they could reboot the server, we took the opportunity to run NETSTAT to view the sockets for clues, but there were less than 20 results. Possibly because they have SQL and IIS on the same server?

This sucks because all we want to do is get an idea of how to duplicate the problem in a controlled environment so we can either a) adjust our ASP accordingly or b) give them a solution that we know addresses the problem.

Thoughts, comments, advice?|||Originally posted by rdjabarov
While many of us here know client connectivity, it's still a SQL Server forum, not SQL Client ;)

I'd follow Satya's suggestions, at least you can see for yourself if you're even getting to the server.
Was the frist comment a suggestion that my question (i.e. how to troubleshoot SQL connectivity issues) is outside of the scope of this forum? If so, please advise a more approriate forum. Thanks.

HELP!

Report services has suddenly refused all access from Internet Explorer (Error
403 - Forbidden).
The only change that has been made to IIS recently (that I am aware of but
others have access as well) is an upgrade from PHP 4 to PHP 5 but other
websites on the same server appear to be working correctly so I'm not
convinced this is the cause of the problem.
Can anyone please shed some light on this or atleast point me in the right
direction to avoid my having to re-install from scratch.
Thanks for any advice.
Ray HojkaWas Reporting Services installed to the default web site?
Perhaps the PHP upgrade program decided to "help" you out with your security
permissions in IIS ?|||Hi Al
Yes RS was installed to the default website. Do you have any idea what
permissions could have been changed. As far as I can tell everything looks
ok on that front but I could well be wrong.
"Al" wrote:
> Was Reporting Services installed to the default web site?
> Perhaps the PHP upgrade program decided to "help" you out with your security
> permissions in IIS ?