Comments
Sort by recent activity
Hi there, Thanks for your reply. I've decided to do it with a custom metric using this scrip: DROP TABLE IF EXISTS #errorLog; CREATE TABLE #errorLog ( LogDate DATETIME, ProcessInfo VARCHAR(64), [Text] VARCHAR(MAX) ); DECLARE @starttime DATETIME = DATEADD(MINUTE, -5, GETDATE()), @now DATETIME = GETDATE() INSERT INTO #errorLog EXEC xp_readerrorlog 0,1,NULL, NULL, @starttime, @now SELECT COUNT(*) FROM #errorLog a WHERE EXISTS ( SELECT * FROM #errorLog b WHERE [Text] LIKE '%I/O requests taking longer than 15 seconds%' AND a.LogDate = b.LogDate AND a.ProcessInfo = b.ProcessInfo ); DROP TABLE IF EXISTS #errorLog; Regards Andrew / comments
Hi there,Thanks for your reply. I've decided to do it with a custom metric using this scrip:DROP TABLE IF EXISTS #errorLog;CREATE TABLE #errorLog( LogDate DATETIME, ProcessInfo VARCHAR(64), ...
I'm having this trouble at the moment as well. What I've noticed is that it doesn't appear to pass the correct password to the Base Monitor service when installing the new version. / comments
I'm having this trouble at the moment as well. What I've noticed is that it doesn't appear to pass the correct password to the Base Monitor service when installing the new version.
I use the GUI to create jobs with a password and it always put this in the options:
PASSWORD = ''<OBFUSCATEDPASSWORD>xxx</OBFUSCATEDPASSWORD>' / comments
I use the GUI to create jobs with a password and it always put this in the options:
PASSWORD = ''<OBFUSCATEDPASSWORD>xxx</OBFUSCATEDPASSWORD>'
I see that too. Maybe try adding the Obfuscated Password from the backup job? / comments
I see that too. Maybe try adding the Obfuscated Password from the backup job?
Latest test for me with SQL Backup v10 (latest patch) and SQL Server 2016 (latest patch). The database is 30Gb with TDE applied to it. Clearly SQL Backup can't be used with a TDE database if you want to also achieve compression on the backups. [image] / comments
Latest test for me with SQL Backup v10 (latest patch) and SQL Server 2016 (latest patch).The database is 30Gb with TDE applied to it.Clearly SQL Backup can't be used with a TDE database if you want...
Hi Don, Thanks for that info. Do you manage to get as good (if not better) compression than using native SQL? / comments
Hi Don,Thanks for that info. Do you manage to get as good (if not better) compression than using native SQL?
I keep looking at this every now and again. The bug I was told by Redgate technical support was with SQL Server rather than SQL Backup. I was wondering if anyone knows if its been fixed yet? / comments
I keep looking at this every now and again. The bug I was told by Redgate technical support was with SQL Server rather than SQL Backup. I was wondering if anyone knows if its been fixed yet?
Is this going to be improved upon? We're currently thinking about using TDE but would have to ditch Redgate as a backup solution as it stands / comments
Is this going to be improved upon? We're currently thinking about using TDE but would have to ditch Redgate as a backup solution as it stands
I appreciate that and have done some testing myself and seem similar results. However, with 2016, Microsoft seem to have solved that issue. I thought the Redgate back program used the VDI so should get the same compression levels as using a BACKUP DATABASE command. / comments
I appreciate that and have done some testing myself and seem similar results. However, with 2016, Microsoft seem to have solved that issue. I thought the Redgate back program used the VDI so should...
I have a similar issue and would also like something like this to happen.
Also I'd like to be able to ignore Microsoft generated objects that are created when I replicate the production database. / comments
I have a similar issue and would also like something like this to happen.
Also I'd like to be able to ignore Microsoft generated objects that are created when I replicate the production database.