How can we help you today? How can we help you today?
stedun

Activity overview

Latest activity by stedun

Windows Server 2003 + Service Pack 2 SQL Server 2005 Standard Edition version 9.00.3077.00 This is from the Windows application event log: Date,Source,Severity,Message,Category,Event,User,Computer 11/06/2009 08:01:48,MSSQL$SQL1,Information,Log was backed up. Database: NetPerfMon<c/> creation date(time): 2009/08/19(08:40:51)<c/> first LSN: 300915:5846:1<c/> last LSN: 301029:24346:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_26AB7443-72D9-4C8A-A77D-EF752ABA31D4'}). This is an informational message only. No user action is required.,Backup,1073760089,MVCIAD\svc-mssql,LALFIMVD0DBS06 11/06/2009 08:00:12,MSSQL$SQL1,Information,Log was backed up. Database: DBA<c/> creation date(time): 2009/04/15(08:22:11)<c/> first LSN: 614:392:1<c/> last LSN: 614:392:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_115D2226-1BF7-478F-952D-3F9C65E8AE77'}). This is an informational message only. No user action is required.,Backup,1073760089,MVCIAD\svc-mssql,LALFIMVD0DBS06 11/06/2009 08:00:05,MSSQL$SQL1,Information,Log was backed up. Database: model<c/> creation date(time): 2003/04/08(09:13:36)<c/> first LSN: 83:120:1<c/> last LSN: 83:120:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_2A05F4E8-A9B3-492F-9CA7-EA7E32504BCF'}). This is an informational message only. No user action is required.,Backup,1073760089,MVCIAD\svc-mssql,LALFIMVD0DBS06 / comments
Windows Server 2003 + Service Pack 2 SQL Server 2005 Standard Edition version 9.00.3077.00 This is from the Windows application event log: Date,Source,Severity,Message,Category,Event,User,Computer ...
0 votes
The previous post is the output from my SQL errorlog where I captured a transaction log backup that starts at 8:00 AM and hangs. It's been running for over 2 hours 45 minutes. / comments
The previous post is the output from my SQL errorlog where I captured a transaction log backup that starts at 8:00 AM and hangs. It's been running for over 2 hours 45 minutes.
0 votes
Date,Source,Severity,Message 11/06/2009 08:01:48,spid117,Unknown,BackupLog: Finished 11/06/2009 08:01:48,spid117,Unknown,Writing backup history records 11/06/2009 08:01:48,Backup,Unknown,Log was backed up. Database: NetPerfMon<c/> creation date(time): 2009/08/19(08:40:51)<c/> first LSN: 300915:5846:1<c/> last LSN: 301029:24346:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_26AB7443-72D9-4C8A-A77D-EF752ABA31D4'}). This is an informational message only. No user action is required. 11/06/2009 08:01:48,spid117,Unknown,BackupLog: Writing history records 11/06/2009 08:01:48,spid117,Unknown,BackupLog: MBC done 11/06/2009 08:01:48,spid117,Unknown,BackupLog: Final configuration done 11/06/2009 08:01:48,spid117,Unknown,BackupLog: Log files done 11/06/2009 08:00:47,spid117,Unknown,BackupLog: Configuration section done 11/06/2009 08:00:47,spid117,Unknown,BackupLog: Work estimate done 11/06/2009 08:00:47,spid117,Unknown,Backup: Streams open 11/06/2009 08:00:46,spid117,Unknown,BackupLog: SafeCheckpoint done 11/06/2009 08:00:45,spid117,Unknown,BackupLog: database NetPerfMon 11/06/2009 08:00:13,spid125,Unknown,FileHandleCache: 0 files opened. CacheSize: 12 11/06/2009 08:00:13,spid125,Unknown,Restore: Configuration section loaded 11/06/2009 08:00:13,spid125,Unknown,Opening backup set 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Finished 11/06/2009 08:00:12,spid117,Unknown,Writing backup history records 11/06/2009 08:00:12,Backup,Unknown,Log was backed up. Database: DBA<c/> creation date(time): 2009/04/15(08:22:11)<c/> first LSN: 614:392:1<c/> last LSN: 614:392:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_115D2226-1BF7-478F-952D-3F9C65E8AE77'}). This is an informational message only. No user action is required. 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Writing history records 11/06/2009 08:00:12,spid117,Unknown,BackupLog: MBC done 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Final configuration done 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Log files done 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Configuration section done 11/06/2009 08:00:12,spid117,Unknown,BackupLog: Work estimate done 11/06/2009 08:00:12,spid117,Unknown,Backup: Streams open 11/06/2009 08:00:12,spid117,Unknown,BackupLog: SafeCheckpoint done 11/06/2009 08:00:12,spid117,Unknown,BackupLog: database DBA 11/06/2009 08:00:09,spid125,Unknown,FileHandleCache: 0 files opened. CacheSize: 12 11/06/2009 08:00:09,spid125,Unknown,Restore: Configuration section loaded 11/06/2009 08:00:09,spid125,Unknown,Opening backup set 11/06/2009 08:00:07,spid117,Unknown,BackupLog: Finished 11/06/2009 08:00:05,spid117,Unknown,Writing backup history records 11/06/2009 08:00:05,Backup,Unknown,Log was backed up. Database: model<c/> creation date(time): 2003/04/08(09:13:36)<c/> first LSN: 83:120:1<c/> last LSN: 83:120:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_2A05F4E8-A9B3-492F-9CA7-EA7E32504BCF'}). This is an informational message only. No user action is required. 11/06/2009 08:00:05,spid117,Unknown,BackupLog: Writing history records 11/06/2009 08:00:04,spid117,Unknown,BackupLog: MBC done 11/06/2009 08:00:04,spid117,Unknown,BackupLog: Final configuration done 11/06/2009 08:00:04,spid117,Unknown,BackupLog: Log files done 11/06/2009 08:00:04,spid117,Unknown,BackupLog: Configuration section done 11/06/2009 08:00:04,spid117,Unknown,BackupLog: Work estimate done 11/06/2009 08:00:04,spid117,Unknown,Backup: Streams open 11/06/2009 08:00:03,spid117,Unknown,BackupLog: SafeCheckpoint done 11/06/2009 08:00:03,spid117,Unknown,BackupLog: database model / comments
Date,Source,Severity,Message 11/06/2009 08:01:48,spid117,Unknown,BackupLog: Finished 11/06/2009 08:01:48,spid117,Unknown,Writing backup history records 11/06/2009 08:01:48,Backup,Unknown,Log was ba...
0 votes
I've enabled the trace flag to capture additional information to the sql errorlog using: DBCC TRACEON (3004, 3605, -1) I'll try to update my post when I capture the next incident. / comments
I've enabled the trace flag to capture additional information to the sql errorlog using: DBCC TRACEON (3004, 3605, -1) I'll try to update my post when I capture the next incident.
0 votes
TLOG Backup hangs with &quot;MSQL_XP&quot; Wait Type
SQL Backup 6.2.0.134 will occasionally have a transaction log backup hang indefinitely. The sqbstatus proc returns nothing. There is no error in the logs I can find. SQL Server's activity monito...
4 followers 18 comments 0 votes
SQL Backup's impact to profile size | Refresh rate
In my user profile, there is a file "1.dat" that is approaching 400 MB. What is it and can I reduce or control its size? ...\Documents and Settings\username\Local Settings\Application Data\Red Gat...
1 follower 1 comment 0 votes