Comments
Sort by recent activity
I have tried again this weekend. Without the trace enabled the CPU resource usage increase is a lot lower. hoovering around 15% on the server running the monitor software (and sql server) and 5% on the second monitored server.
I will try to move the sql response monitor software/ repository to a machine which is not used a lot.
I'm wondering how many licenses will we need for this? One machine just running the sql response monitor/repository and two machines which are monitored? / comments
I have tried again this weekend. Without the trace enabled the CPU resource usage increase is a lot lower. hoovering around 15% on the server running the monitor software (and sql server) and 5% on...
Destination:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Source:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Can this last patch be an issue? / comments
Destination:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4...
The error is raised during logshipping and after the file is copied from backup location to the destination server.
I discoverd that the databas was still (2.8 GB ) loading on the secondairy machine where the error was raised when sqb transaction logs where restored.. This raised this same error. I will retry the restores again after the first initial restore is loaded and fully (readonly) operational.. I guess the error will dissapear then.
[edit]
I do have a different error description just mailed to me:
09/05/2006 17:50:01: Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860
09/05/2006 17:50:01: Server: Msg 3013
BACKUP LOG is terminating abnormally.
09/05/2006 17:50:01: Server: Msg 3241
The media family on device 'SQLBACKUP_BBE3F288-793E-42C5-B181-B7157546D398' is incorrectly formed. SQL Server cannot process this media family.
09/05/2006 17:50:01: Failed to close vdi.
[/edit]
so I might just have another issue then... / comments
The error is raised during logshipping and after the file is copied from backup location to the destination server.
I discoverd that the databas was still (2.8 GB ) loading on the secondairy mach...
And on your advice tested with IE9 (win7) and its fast.
Definitively an issue with chrome and Sql Monitor web app.
It is especially when hitting the alerts tab and opening an alert.
We only have 3 monitored servers, sql monitor on a complete separate infra. / comments
And on your advice tested with IE9 (win7) and its fast.
Definitively an issue with chrome and Sql Monitor web app.
It is especially when hitting the alerts tab and opening an alert.
We only have 3 ...