Comments
Sort by recent activity
Update:
I just recycled the SQL Server service and now I no longer get the warning.
For future reference, is there a better way? / comments
Update:
I just recycled the SQL Server service and now I no longer get the warning.
For future reference, is there a better way?
I too am getting this error.
11/12/2008 5:00:05 PM: Warning 167: Failed to get database size from server.
11/12/2008 5:00:05 PM: SQL error 913: Could not find database ID 38. Database may not be activated yet or may be in transition.
The backups are fine, but the warning is anoying. This started happening when the database was deleted and a new database with the same name was created. The database in question now has an ID of 35 not 38. So how do I fix this?
BTW, I did run the script posted earlier to clear out the history, but the problem remains.
EXEC master..sqbdata 'DELETE FROM backuplog WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''MyDBName'')'
EXEC master..sqbdata 'DELETE FROM backupfiles WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''MyDBName'')'
EXEC master..sqbdata 'DELETE FROM backuphistory WHERE dbname = ''MyDBName''' / comments
I too am getting this error.
11/12/2008 5:00:05 PM: Warning 167: Failed to get database size from server.
11/12/2008 5:00:05 PM: SQL error 913: Could not find database ID 38. Database may not be ac...
http://sirsql.net/blog/2011/9/26/optimi ... tores.html
BTW, I did find that increasing the thread count helped a lot too. It did increase the buffer count to by 6 * Threadcount up to 28 buffers max, which sped the redo phase up. But I do think that that if SQL Server allows up to a 4MB transfer size natively then Red Gate SQL Backup should allow it too. I'm not suggesting that you change the 1MB default, but should allow for manual adjustment of MaxTransferSize and buffercount parameters. / comments
http://sirsql.net/blog/2011/9/26/optimi ... tores.html
BTW, I did find that increasing the thread count helped a lot too. It did increase the buffer count to by 6 * Threadcount up to 28 buffers ma...
Thanks for the response Chris. Unfortunately the link you sent is not helping with the problem. It seems to imply that I need to bump up the user connection settings at the database server; however, it is already configured to 0 (0 = unlimited). All research I have performed on this problem, indicates that the default limit for ADO.Net is 100 connections, and when I run a netstat from the base monitor and count the numbers of connections into the repository DB is exactly at 100. The research indicates that this can only be increased in the application.
If I am missing something else to check at the server (other than user connections setting) please specifically let me know.
Back to my original questions, is there a way I can bump up the value of max pooled connections via a configuration change in the Base Monitor? / comments
Thanks for the response Chris. Unfortunately the link you sent is not helping with the problem. It seems to imply that I need to bump up the user connection settings at the database server; howev...
For the benefit of anyone reading this thread, I was able to resolve this issue in a support ticket with Red Gate.
Here was the resolution: "Chris Kelly (Support)
Dec 17 16:39 (GMT)
Thank you for your reply.
You could try the following.
• Stop the SQL Monitor Base Monitor service
• locate the file: RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config
found here on the SQL Monitor Base Monitor machine: C:\ProgramData\Red Gate\SQL Monitor 3
• Make a copy of the file just in case you decide to reverse the changes. Any incorrect changes to this file can prevent the service from starting.
• locate the <connectionStrings> tag, should be around line 110.
• in the line starting "<add name="DataConnectionString"" find the entry "Packet Size=4096;" and add the setting "Max Pool Size=1000;"
• Save the file and Restart the SQL Monitor Base Monitor service.
The change can easily be reversed by deleting the edited file and renaming the copy. You can also adjust the "Max Pool Size" as you see fit.
Chris Kelly
Technical Support Engineer
"[/i] / comments
For the benefit of anyone reading this thread, I was able to resolve this issue in a support ticket with Red Gate.
Here was the resolution:"Chris Kelly (Support)
Dec 17 16:39 (GMT)
Thank you for yo...
I second that request. I do have a cluegy work around but agree it would be better if they stop running auto refresh and turn off client side caching altogether. It's much faster to just query the data you need from the server when you need it. Especially when you have many instances and databases.
Here is the work around: Create a group for each instance and put the instance in that group.
I know, this is a real pain to do, but at least auto refresh does not kick in until you open the given group. / comments
I second that request. I do have a cluegy work around but agree it would be better if they stop running auto refresh and turn off client side caching altogether. It's much faster to just query th...
Yes, that helps.
In my case I was able to further take this information and query my Central Management server to generate the XML data needed.
Since I have a naming convention on the different environments, it was simply a matter of parsing the environment value from the name. I am providing it for the benefit of anyone else interested.
Obviously this query needs to be modified to meet the convention of a given organization's naming conventions, but here's a start. Modify as needed the output from this query below and paste results into the XML file following the <?xml version="1.0"?> line.
SELECT name
,category = CASE LEFT(name, 1)
WHEN 'D' THEN 'DEVELOPMENT'
WHEN 'S' THEN 'STAGING'
WHEN 'T' THEN 'TESTING'
WHEN 'P' THEN 'PRODUCTION'
ELSE 'PRODUCTION'
END
FROM msdb.dbo.sysmanagement_shared_registered_servers_internal
FOR XML PATH('server')
,ROOT('settings') / comments
Yes, that helps.
In my case I was able to further take this information and query my Central Management server to generate the XML data needed.
Since I have a naming convention on the different env...
The labs link is for the 6.4.0.56 version of the converter tool. But, yes it does work. Can you repair the corrupted current version (7.3.2.3) for future releases? / comments
The labs link is for the 6.4.0.56 version of the converter tool. But, yes it does work. Can you repair the corrupted current version (7.3.2.3) for future releases?
Wow!!!!
After upgrading both the client and Server components to 7.3.1.1, the history comes up blazingly fast. It's been turbo charged. Good job!!! [image] / comments
Wow!!!!
After upgrading both the client and Server components to 7.3.1.1, the history comes up blazingly fast. It's been turbo charged.Good job!!!