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
No comments:
Post a Comment