Comments
Sort by recent activity
Trace start and stop events are logged in the SQL Server error log by default.
SQL Monitor starts and stops a new trace every 5 min. This is done so we can keep a rolling trace buffer of between 10 and 15min of data rather than creating a single very large trace file.
Cheers,
--
Daniel / comments
Trace start and stop events are logged in the SQL Server error log by default.
SQL Monitor starts and stops a new trace every 5 min. This is done so we can keep a rolling trace buffer of between 10...
I've seen this happen before when people have multiple installs of the SQL Monitor Base Service.
You might be using the same database to store the data for your two installs.
Go to "Configuration" > "About"
Near the bottom of the page should be a line starting with "Database" this will tell you which server is hosting the SQL Monitor Data Repository database.
Log into that database server and run sys.sp_who2 and check the HostName and ProgramName columns. SQL Monitor uses "SQL Monitor - Repository" as the application string.
It is very important that each install of SQL Monitor uses is own storage database.
--
Daniel / comments
I've seen this happen before when people have multiple installs of the SQL Monitor Base Service.
You might be using the same database to store the data for your two installs.
Go to "Configuration" ...
It would also be worth trying to deleting
C:\ProgramData\Red Gate\SQL Monitor 2\Red Gate Monitor.pfx
then restarting the iis section of SQL Monitor.
Cheers,
--
Daniel / comments
It would also be worth trying to deleting
C:\ProgramData\Red Gate\SQL Monitor 2\Red Gate Monitor.pfx
then restarting the iis section of SQL Monitor.
Cheers,
--
Daniel
Hi,
Could you check that you have configured IIS to use the DefaultAppPool with SQL Response and that the DefaultAppPool is using the Integrated Managed Pipeline Mode and is running as the ApplicationPoolIdentity.
Cheers,
--
Daniel / comments
Hi,
Could you check that you have configured IIS to use the DefaultAppPool with SQL Response and that the DefaultAppPool is using the Integrated Managed Pipeline Mode and is running as the Applicat...
Hi Viral,
We've rolled this fix into the a new release of SQL Monitor.
Please re-download the installer from http://www.red-gate.com/products/dba/sq ... r/download
Cheers,
--
Daniel / comments
Hi Viral,
We've rolled this fix into the a new release of SQL Monitor.
Please re-download the installer from http://www.red-gate.com/products/dba/sq ... r/download
Cheers,
--
Daniel
Hi Rhys,
We have a known issue where the upgrade from 2.2 to 2.3 can get stuck. The last item in the table should be Seq50 rather than Seq42. We have a patch but it will take until early next week before we can release it.
Luckily we have a work around you can deploy as a SQL Script. Drop me an email at daniel.kenyon-jones [AT] red-gate.com and I'll send it to you.
You'll need to make sure you've tracked down all the instances of SQL Monitor you've installed and stop them before running the script. EXEC sys.sp_who2
will show you which hosts are accessing the database.
Cheers,
--
Daniel / comments
Hi Rhys,
We have a known issue where the upgrade from 2.2 to 2.3 can get stuck. The last item in the table should be Seq50 rather than Seq42. We have a patch but it will take until early next week ...
Hi Rhys,
Please run the following query in SMMS on your SQL Monitor database and post the results: SELECT Id ,
Date ,
CodeVersion ,
SchemaVersion FROM versioning.SchemaVersionHistory
Thanks,
--
Daniel / comments
Hi Rhys,
Please run the following query in SMMS on your SQL Monitor database and post the results:SELECT Id ,
Date ,
CodeVersion ,
SchemaVersion FROM versioning.SchemaVersi...
Hi PDinCA,
We're currently looking at this issue and trying to find the very narrow balance between being a reliable fault tolerant monitoring system and a good network and security citizen.
The behaviour your describing what SQL Response 1.x would do when it encountered a security issue. It would just retry constantly. One of our customer didn't notice that the password on the domain account that SQL Response was using had expired. SQL Response merrily tried to connect over and over again. This customer also had and intrusion detection system set to email them if someone was trying to hack their systems. Each failed login generated multiple emails which eventually acted as a denial of service attack against there internal email server :shock:. There email server fell over. The customer was less than pleased.
Because of this, we opted to take the opposite view for SQL Response 2.x. We made the assumption (naively) that customers would have redundant domain controllers and when Windows and SQL Server tell us that credentials are invalid they really are invalid. SQL Response currently halts monitoring when it receives an authentication error as we assumed that this couldn't correct it self without human intervention. We also don't like the idea of taking out peoples' email server [image] .
We've had a few reports of this recently and we are working some sort of configuration option so people can disable this behaviour. We will probably revisit this in a future version of SQL Monitor.
Thanks for your feedback and we will let you know when we have a work around for this.
--
Daniel KJ / comments
Hi PDinCA,
We're currently looking at this issue and trying to find the very narrow balance between being a reliable fault tolerant monitoring system and a good network and security citizen.
The be...
Hi Wedoxin,
It's a bit off topic, but if you want to force all your computers to use a certain DNS server then it sounds like group policy would do the job.
See http://support.microsoft.com/kb/294785 for more information.
Cheers,
--
Daniel / comments
Hi Wedoxin,
It's a bit off topic, but if you want to force all your computers to use a certain DNS server then it sounds like group policy would do the job.
See http://support.microsoft.com/kb/2947...
Hi,
Sorry, I got that last post the wrong way round. Please restart those services on the host of the instance you are trying to monitor.
Cheers,
--
Daniel / comments
Hi,
Sorry, I got that last post the wrong way round. Please restart those services on the host of the instance you are trying to monitor.
Cheers,
--
Daniel