Comments
Sort by recent activity
I guess that makes sense.
FYI, all of these databases are Auto restores using SQL Backup 7, from most recent backup of each db with _Restore appended to the name, then dropped after success
1. Page Verify is set to CheckSum on all databases being backed up
2. Yes, all are ended
3. The name is the same after each restore, but the db is dropped immediately.
It seems, to make it stop, that I need to restore each db without drop, then drop alerting from the config for that db, then drop the db, and carry on. Will that work, even though the config won't be visible when the db isn't present? Is there a way to alter the config when the db isn't present? ideally I'd like to do it for one, then perhaps open a text file and copy past the other 9 or 27 dbs in, to save me the effort of actually restoring each db. / comments
I guess that makes sense.
FYI, all of these databases are Auto restores using SQL Backup 7, from most recent backup of each db with _Restore appended to the name, then dropped after success
1. Page...
How do I clear the configuration settings for databases that are no longer present?
I tried my idea of restoring the db, then adjusting the config to ignore, then dropping the db, and it didn't work, but now I can't delete the config, and I'm getting this error message:
DESCRIPTION: Could not find database ID 37. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. / comments
How do I clear the configuration settings for databases that are no longer present?
I tried my idea of restoring the db, then adjusting the config to ignore, then dropping the db, and it didn't wor...
I tried the restore of one of the database, then turned off the alerts, then dropped the database, to see if my idea would work. It didn't. I guess I'm not that surprised, each restore probably gets a new databaseID, and I imagine your configuration uses that ID to match when alerts are triggered. I can hear you say 'just ignore them' from here. I always fear alert fatigue. / comments
I tried the restore of one of the database, then turned off the alerts, then dropped the database, to see if my idea would work. It didn't. I guess I'm not that surprised, each restore probably g...
I have a reporting database, and I need the 5+ columns in my reporting tables to add up to a specific number, specifically 100%. I guess I could PIVOT a 3 column layout with ID, PercentGroup, Value but I would still need the column sections within each ID to add up to 100% before I PIVOT it.
Please consider this in your next development cycle / comments
I have a reporting database, and I need the 5+ columns in my reporting tables to add up to a specific number, specifically 100%. I guess I could PIVOT a 3 column layout with ID, PercentGroup, Valu...
domager wrote:
I'm having the same problem here but with the SQL Search 2 tool, I've recently rebuilt my machine, I'm running Win2008R2.
I first installed SSMS 2012 and then installed the SQL Search 2 tool, and all was working fine.
After finding SSMS 2012 a little sluggish I decided to install SSMS 2008 R2, but the Red Hat menu wasn't showing as an option, so I removed SQL Search 2 and reinstalled, but again it hasn't appeared in 2008, working fine in 2012 though.
Did this get resolved...?
It did. They sent me the latest version at the time '2.0.1.28' and all was well.
Which version are you on? / comments
domager wrote:
I'm having the same problem here but with the SQL Search 2 tool, I've recently rebuilt my machine, I'm running Win2008R2.
I first installed SSMS 2012 and then installed the SQL Se...
domager wrote:
Random Lengths wrote:
It did. They sent me the latest version at the time '2.0.1.28' and all was well.
Which version are you on?
Looks like I'm on a slightly newer version than you, v2.0.1.30
Sorry, I don't know what else to tell you, other than to contact support. They've always been quick to respond for me. / comments
domager wrote:
Random Lengths wrote:
It did. They sent me the latest version at the time '2.0.1.28' and all was well.
Which version are you on?
Looks like I'm on a slightly newer version t...
I was installing and reinstalling 2.0.1.8. But I tried uninstalling, then reinstalling 1.1.10.484, then installing 2.0.1.8.
My Tab History toolbar is back, but search is still missing.
After restarting SSMS this last time, I got 2 new error messages, perhaps they are related to the issue:
[img]c:\users\dlg\desktop\2014-04-24_13-12-25.jpg[/img]
[img]c:\users\dlg\desktop\2014-04-24_13-12-13.jpg[/img]
Though both mention RedGate.SQLSourceControl.SSMS2012.Addin and SQL Source Control seems to be working fine. / comments
I was installing and reinstalling 2.0.1.8. But I tried uninstalling, then reinstalling 1.1.10.484, then installing 2.0.1.8.
My Tab History toolbar is back, but search is still missing.
After resta...
I'm having the same issue with the Beta. I had it working with my SSMS 2008R2, and when I upgraded SSMS to 2012, SQL Search is now gone. I tried the SSMS Integration Pack Framework 1 Repair suggested, and it didn't work.
MUST HAVE MY SEARCH [image] / comments
I'm having the same issue with the Beta. I had it working with my SSMS 2008R2, and when I upgraded SSMS to 2012, SQL Search is now gone. I tried the SSMS Integration Pack Framework 1 Repair sugge...
That does what a want, Thanks.
Just a feature note, the context menu is less intuitive then the ubiquitous checkbox at the top like in SQL Compare uses. Rarely is it a good idea to implement the same feature differently in your own products. / comments
That does what a want, Thanks.
Just a feature note, the context menu is less intuitive then the ubiquitous checkbox at the top like in SQL Compare uses. Rarely is it a good idea to implement the s...
I'm not sure I agree with you. When I drill down on my other DBs, the long-running-query alert shows up fine for those DB's, it's only the master DB that this doesn't work for.
james.billings wrote:
You're not being crazy- I see the same thing. I think there's an explanation though.
The Long Running Query alert is an Instance-Level alert. If you go to the screen to configure alerts, you'll see once you drill down to a specific database, you cannot configure that particular query.
This works the same when viewing the alerts- as you drill down, you'll see it at the instance level, but once you select an individual database, you'll only see alerts that are DB - level. So although the alert knows which DB raised the fault, the alert isn't occurring at the DB level.
I probably didn't explain that very well, and it's not obvious this happens from the screen, but hopefully it makes sense!
/ comments
I'm not sure I agree with you. When I drill down on my other DBs, the long-running-query alert shows up fine for those DB's, it's only the master DB that this doesn't work for.
james.billings wro...