Comments
Sort by recent activity
The OS is Windows Server 2012 Standard edition.
SQL server is SQL Server 2012, als standard edition.
Regards,
Tom / comments
The OS is Windows Server 2012 Standard edition.
SQL server is SQL Server 2012, als standard edition.
Regards,
Tom
I understand the desission, but it would be nice to have some kind of override for this.
Regards,
Tom / comments
I understand the desission, but it would be nice to have some kind of override for this.
Regards,
Tom
Brian,
Thanks for your sugestion.
I wil give it a try, but this will probably not be a solution for us, as the timeline is the most important part of the GUI for us.
Because we have to backup 40.000 databases (1 fullbackup every 24 hour, and a transactionlog backup every hour) we use the timeline interface to monitor the timing progress of our backups.
This timeline is 1 of the reasons we use SQL backup.
Regards,
Tom / comments
Brian,
Thanks for your sugestion.
I wil give it a try, but this will probably not be a solution for us, as the timeline is the most important part of the GUI for us.
Because we have to backup 40.00...
Brian,
I have tried te registry key and this did disabed the timeline and reduced the memory usage of the proccess (to about 150-200 MB).
But ass explained in my previous post this is not a solution for us, as the timeline is the main reason for us to use the GUI.
Regards,
Tom / comments
Brian,
I have tried te registry key and this did disabed the timeline and reduced the memory usage of the proccess (to about 150-200 MB).
But ass explained in my previous post this is not a solutio...
Brian,
I don't think, the inegrety check flaged is raiser bij restoring the backup, i just think SQL Response stopped checking this database because of the restore (maybe because the databses has a new db_id after the restore ?).
The integrity check overdue was already flagged before we restored the DB, but it seems it stopped checking this issue as
Last checked : More Then a day ago
I checked the licence activition, and it seems ok, also all recommandations for other databases (about 100) on this server are working fine
SQL errorlog is available normaly
We did not do any upgrade as we just started using SLQ response. Also this server is a fresh installed SQL 2008 on a new Windows 2008R2 sever / comments
Brian,
I don't think, the inegrety check flaged is raiser bij restoring the backup, i just think SQL Response stopped checking this database because of the restore (maybe because the databses has a...