Activity overview
Latest activity by linque
Do the "Select" drop down like you're going to clear all of the alerts, and choose ALL. Once you do that, you will see the option. [image] / comments
Do the "Select" drop down like you're going to clear all of the alerts, and choose ALL. Once you do that, you will see the option.
I'm an idiot. There is an option to check all alerts (not just the ones showing) that was right in front of my face the entire time. I'm good now. :oops: / comments
I'm an idiot. There is an option to check all alerts (not just the ones showing) that was right in front of my face the entire time. I'm good now. :oops:
Mass Update to Clear 66,000 Alerts
I woke up at 3:30 this morning to about 66,000 "SQL Server error log entry" alerts about the transaction log file being full on one of my hosted databases. Thank goodness SQL Monitor stops sending ...
I had to have the SAN admin give me another 100GB since the tempdb.ldf file grew to 70 GB, and it did eventually free up about 60 GB. The db shrink was taking forever, though, so I decided to just drop the database and let it create a new one. Setup is really simple, so it didn't take long to reconfigure things. I made sure to set the data purge at 2-months retention this time.
Thx / comments
I had to have the SAN admin give me another 100GB since the tempdb.ldf file grew to 70 GB, and it did eventually free up about 60 GB. The db shrink was taking forever, though, so I decided to just...
Manually Purge Old Data
I'm running SQL Monitor 2.3.0.334, and neglected to set up Data Purging when I first set it up. I've been slowly setting the purge dates from one-year to six-months to three-months so I don't over...
The database server was crawling when I got in this morning, and users were complaining about not being able to use apps that had databases on that server. I did receive an email from RG Support with a link about my issue, but it's too late now unfortunately. www.red-gate.com/supportcenter/Content? ... %20Monitor
The database was created on 02/08/2011, and is currently monitoring 8 servers and 8 instances. I should have set a purge policy long ago to avoid all this. A reboot seems to have cleared things up. I also got more memory and 2 additional procs added to my server -- bonus!
I'm going to let it run for a bit, then revisit the purge properties later. I do have 1659MB of free space now (out of 72064 MB) on the SQL Monitor MDF file. I only had about 20MB free before the purge started.
P.S. I still love SQL Monitor! / comments
The database server was crawling when I got in this morning, and users were complaining about not being able to use apps that had databases on that server. I did receive an email from RG Support w...
tempdb Growing Alarmingly Fast!
I upgraded to version 2.3.0.334 earlier today, and decided to purge my data after the installation completed. I've never purged the database before, and my data file for SQL Monitor was about 70GB...
SQL Monitor 2.3.0.334 Email Issue With Exchange 2010
So I finally got around to upgrading from 2.2.0.260 to 2.3.0.334 on one of my two SQL Monitor servers. Everything went smoothly during the upgrade, however, we recently upgraded our Exchange serve...
Woo hoo! They are both working now. / comments
Woo hoo! They are both working now.
Well, I upgraded both instances and can now see one. Looks like the upgrade helped, but I think I'm also having a WiFi issue. Thanks for your help, Chris! / comments
Well, I upgraded both instances and can now see one. Looks like the upgrade helped, but I think I'm also having a WiFi issue. Thanks for your help, Chris!