Comments
Sort by recent activity
RBA,
We are very pleased with the product but we are also seeing that this CPU issue is very bad. Are there some steps we can take to troubleshoot or at least provide your team with the necessary information to investigate some of this?
I ran the ANTS profiler on the environment that's monitoring our dev servers and saw (what i thought was a lot) of exceptions being thrown.
Our other environment was pegged at 99% CPU almost constantly after running for about a week and then when I tried to stop the base monitor process it crashed.
I think if we're going to move forward on this product we'd need to know that this CPU issue was being seriously looked at and there are some hard steps being taken to resolve some of it.
Let me know what information I can provide you to start investigating these issues.
Thanks! / comments
RBA,
We are very pleased with the product but we are also seeing that this CPU issue is very bad. Are there some steps we can take to troubleshoot or at least provide your team with the necessary ...
Oh! I didn't even realize that! So basically whatever level I'm clicked on (server, instance, group) that is the level that the setting will apply to. Got it!
Thanks!
Is there any estimated release date for SQLMonitor v2.2? / comments
Oh! I didn't even realize that! So basically whatever level I'm clicked on (server, instance, group) that is the level that the setting will apply to. Got it!
Thanks!
Is there any estimated relea...
I would like to expand on this. I think a helpful feature would be to have login management that incorporates department level management of the servers. The goal being that you can assign certain servers (or groups) to specific departments and have department level logins (or company level if you're using it to monitor different company servers). This way you can have one or more administrative logins that can see / manage everything and then assign out department / company level logins that can be read-only. These department level logins would only be able to see their servers of interest through the UI.
Also make sure to tie in the alert system to the department's alert e-mail so both the administrator and that department receive alerts for their servers.
This would be extremely helpful in many cases. / comments
I would like to expand on this. I think a helpful feature would be to have login management that incorporates department level management of the servers. The goal being that you can assign certai...
RBA,
Right now we're just testing so we have 6 servers on one test environment with about 50-120 databases which would be similar to production (except in production we'll have about 20 servers) and we have another test environment with about 10 servers and about 10-25 databases per server which is more similar to our dev environment.
The databases are all fairly small (< 8 GB) but they have a large number of objects in them (procedures, tables, etc...).
So I think once we purchase we're looking to get about 30 servers monitored.
The trace I sent you was for the smaller environment that mimics our testing environment but i'm seeing similar CPU usage on both. / comments
RBA,
Right now we're just testing so we have 6 servers on one test environment with about 50-120 databases which would be similar to production (except in production we'll have about 20 servers) an...
Here's a sendspace link to a saved, short ANTS profiler trace of the base monitor service on my local machine. I also included the html output. http://www.sendspace.com/file/s0o579 / comments
Here's a sendspace link to a saved, short ANTS profiler trace of the base monitor service on my local machine. I also included the html output.http://www.sendspace.com/file/s0o579
Priya,
Remote Monitor is EXACTLY what we'd need for our environment. That's terrific that you're already working on that solution. If we purchase v2.1 would we be eligible for the v2.2 upgrade to include Remote Monitor? (or is that a question I'd need to ask sales?)
Also, does your company make a product to monitor web servers (similar to the SQL monitor)?
Thanks again and we look forward to the RM product!!
John / comments
Priya,
Remote Monitor is EXACTLY what we'd need for our environment. That's terrific that you're already working on that solution. If we purchase v2.1 would we be eligible for the v2.2 upgrade to...
Priya,
I would think that not alerting on the issue would probably be the way to go since there is nothing actionable that can realistically be done to resolve the matter.
Thank you so much for the information and logging the SRP, you guys are great!
John / comments
Priya,
I would think that not alerting on the issue would probably be the way to go since there is nothing actionable that can realistically be done to resolve the matter.
Thank you so much for the...
I ran the exact code you posted above and just replaced the path with a path to one of our files. I'm still getting the same error "Syntax error: 'SINGLERESULTSET' after 'WITH'"
File version of SQBCoreService.exe is 5.1.0.2781
When I go to help > about it says I'm using Red-Gate SQLBackup 5.4.0.55
Windows version is Windows Server 2003 Enterprise Edition x64 SP2
SQL Server is SQL Server 2005 Standard Edition x64 SP3 CU1
(9.0.4207)
Please let me know if you need any other information.
Thanks!
John / comments
I ran the exact code you posted above and just replaced the path with a path to one of our files. I'm still getting the same error "Syntax error: 'SINGLERESULTSET' after 'WITH'"
File version of SQ...
I'm trying to use it for the RESTORE HEADERONLY command. I need to extract information from the header in order to do what I need to do.
John / comments
I'm trying to use it for the RESTORE HEADERONLY command. I need to extract information from the header in order to do what I need to do.
John
About 5 min after I posted it I realized I was putting the ending double quote right after the path which was excluding the WITH SINGLERESULTSET command.
Now my problem is that in SQLBackup 6.0+ it works fine but in SQLBackup 5.4.0.55 I'm getting a syntax error saying that there's a syntax error SINGLERESULTSET after WITH. But it says this is supported since 5.3. Can anyone tell me if this is a mistake?
John / comments
About 5 min after I posted it I realized I was putting the ending double quote right after the path which was excluding the WITH SINGLERESULTSET command.
Now my problem is that in SQLBackup 6.0+ it...