Comments
Sort by recent activity
Hi Litu,
There is an option to Ignore Constraint and index names. When you are editing the compare project you can find this on the Options tab (the last tab) under Ignore (it is the fourth option down).
I hope this helps. Let me know if you need any further assistance. / comments
Hi Litu,
There is an option to Ignore Constraint and index names. When you are editing the compare project you can find this on the Options tab (the last tab) under Ignore (it is the fourth option...
Hi Craig,
Are you able to provide any details of what the loading process entails (process, scripts, etc)? If it isn't changing the recovery model (which I wouldn't expect it to switch from simple either, but you never know) then something seems to be causing Monitor to think it has and I need to know what that is so I can reproduce the issue.
Alternatively you can just disable that Alert for the affected databases (http://documentation.red-gate.com/display/SM4/Configuring+alerts).
Kind regards,
Alex / comments
Hi Craig,
Are you able to provide any details of what the loading process entails (process, scripts, etc)? If it isn't changing the recovery model (which I wouldn't expect it to switch from simple...
Hi Craig,
I have had no luck still in recreating this, bar having the Recovery model change. Are you aware of any maintenance tasks or other jobs occurring at around the times that the alert is being raised (6:00 AM or 15:30 PM)? / comments
Hi Craig,
I have had no luck still in recreating this, bar having the Recovery model change. Are you aware of any maintenance tasks or other jobs occurring at around the times that the alert is bei...
Hi Craig,
Can you also check the Properties > General page tab for Datawarehouse4 and check the timestamps for both backup and log backup there (screenshot or otherwise)? I just want to ensure there isn't some errant process occurring that is switching between the different recovery modes for some odd reason. I'll continue replicating your setup as I can in the meantime.
Kind regards,
Alex Bartley
Product Support Engineer / comments
Hi Craig,
Can you also check the Properties > General page tab for Datawarehouse4 and check the timestamps for both backup and log backup there (screenshot or otherwise)? I just want to ensure the...
Hi Craig,
I have tried various ways to get SQL monitor to create a 'log backup overdue' alert for a database using the simple recovery model but have not had any success. It would only alert after I had switched the database to Full recovery model (and performing some action) before switching back to the simple recovery mode. Can you provide any further details (sql server version, logs from sql monitor, screenshot of the properties > options section for the specified database, etc)?
Kind regards,
Alex Bartley
Product Support Engineer / comments
Hi Craig,
I have tried various ways to get SQL monitor to create a 'log backup overdue' alert for a database using the simple recovery model but have not had any success. It would only alert after ...
Hi Elsio,
This is occurring because the seed value is at the lower limit of the in32 data type (–2147483648). To get back to this point, with the stated increment value of 1, it needs to set the seed to be –2147483649 so that when it increments it for the first row of data it starts off at the seed value. The problem is that –2147483649 is out of the range of the int32 datatype. If you set the seed value to be –2147483647 it should not error.
I hope this helps!
Kind regards,
Alex / comments
Hi Elsio,
This is occurring because the seed value is at the lower limit of the in32 data type (–2147483648). To get back to this point, with the stated increment value of 1, it needs to set the...
For anyone who may run into this issue a new version has recently been released on 18 Feb 2015 that addresses the issue. Please download version 4.1.1.35 here and see the release notes here.
Kind regards,
Alex / comments
For anyone who may run into this issue a new version has recently been released on 18 Feb 2015 that addresses the issue. Please download version 4.1.1.35 here and see the release notes here.
Kind ...
Hi all,
David, I worked with you on the support ticket last week which didn't directly address this (we got it working on the later version that wasn't getting this issue) but having seen this outstanding, I thought I would update it for anyone else experiencing this issue.
****This only applies to versions before 7.0.5****
I believe this error: "Authentication failed because the remote party has closed the transport stream." is related to not having TLS 1.0 and/or SSLv3.0 enabled on the system running the SQL Monitor Base Monitor and SQL Monitor Web Service services. This post goes over the registry settings to enable both the client and server portions of TLS1.0 and SSLv3.0.
You may also need to ensure that the user running the SQL Monitor Web Service (or the application pool identity for IIS installs) has the permissions from this page and in some circumstances those listed by Brian above as well.
****In Versions 7.0.5 and later****
SQL Monitor supports all TLS versions and SSLv3.0 in this order: TLS1.2, TLS1.1, TLS1.0 and finally SSLv3
I hope that helps!
Kind regards,
Alex / comments
Hi all,
David, I worked with you on the support ticket last week which didn't directly address this (we got it working on the later version that wasn't getting this issue) but having seen this outs...
Yes I realise this is a bit out of date / late.
From what I have seen this appears to be an issue with IIS setup - I have recently encountered this and found that using the XSP server connected properly. I have not yet identified the exact bit that has gone wrong, but thought I would update this since I have some information.
Kind regards,
Alex / comments
Yes I realise this is a bit out of date / late.
From what I have seen this appears to be an issue with IIS setup - I have recently encountered this and found that using the XSP server connected pro...
Hello all,
I know it's quite a bit after the fact, but for anyone reading I wanted to mention the documentation has now been updated to include the need for db_datareader and db_datawriter on tempdb.
Kind regards,
Alex / comments
Hello all,
I know it's quite a bit after the fact, but for anyone reading I wanted to mention the documentation has now been updated to include the need for db_datareader and db_datawriter on tempd...