Index was outside the bounds of the array

Undo for SQL Server.

Moderator: eddie davis

Index was outside the bounds of the array

Postby AlexG » Tue Jul 18, 2006 10:57 pm

Hi,
using latest version of your product.
I want to find delete query in log files.

DB is 50GB , log created every 15 min size (400 KB - 300 MB)
full backup done to Tivoli, log backup done to disk, all log files 2 days
older then full backup deleted from disk

stared new project waited till all files examined , got message no Full backup , then application start to analyze log files ,after 5 minutes got message "Index was outside the bounds of the array"

my questions
1. does application needs acess to full backup file ?
2. is it possible to simply read data from from single log file?
3. cause of error above ?

Thanks
AlexG
AlexG
 
Posts: 14
Joined: Fri Apr 07, 2006 7:07 pm

Postby AlexG » Wed Jul 19, 2006 10:22 pm

Found work around ,but still have few questions

1. deleted backup history older then 7 days

started project -> point on db -> wait till all log files checked-> remove all -> add only log files from my location

here come tricky part
test 1
total number of log files added = 64, biggest 480 MB
application started analayze files and then return exeption

test 2
total number of log files added = 30 and I excluded 480 mb log file ,
range 2006/07/18 00:00 to 2006/07/18 16:00
application analyzed logs and active log(600MB) ,took about 25 minutes
to compete and I got window with all records modified.

1. Is any limit to number of log files that could be analyzed ?
2. user infromation shows only dbo , I guess the is no info about host name ,nt name available in log files?
AlexG
 
Posts: 14
Joined: Fri Apr 07, 2006 7:07 pm

Postby Brian Donahue » Tue Jul 25, 2006 4:39 pm

Hi Alex,

I'm not aware of any hard-coded limit on the number of log backups that you can include in the log anaylsis, please correct me if I'm wrong.

If anything bad happens, it's probably because you don't have enough resources available (RAM, disk space...). Log Rescue can pound your local disk caching extracted information from the log file and/or backup files.

There's a funny issue to do with usernames in the SQL Server logs. Sometimes the username is not recorded, in these cases, log rescue calls the user unrecorded because the log identifies him with a userid of -1. For users that can be resolved to a user name, Log Rescue identifies any user that is part of the db_owner role as DBO. Otherwise, normal SQL users are listed in the analysis.

I hope this helps!
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Log Rescue

Who is online

Users browsing this forum: No registered users and 1 guest