Comments
Sort by recent activity
Hi Chris (fellow Brit),
Windows Server 2008 Enterprise.
Regards,
Stephen / comments
Hi Chris (fellow Brit),
Windows Server 2008 Enterprise.
Regards,
Stephen
Yes, I was using the .exe as quoted.
No, I'd completely forgotten about disabling the cluster resource on the passive node - not overly familiar with cluster management as I'm only an accidental DBA.
Could I ask Red Gate to "Please add a dialog box so that when upgrading a SQL Backup Server component on a Passive node it reminds (forgetful/inexperienced/non-admin) users to disable the cluster resource temporarilly." This will help IMMENSELY and prevent others making the same mistake I did!
Cheers!
Stephen / comments
Yes, I was using the .exe as quoted.
No, I'd completely forgotten about disabling the cluster resource on the passive node - not overly familiar with cluster management as I'm only an accidental DB...
SQL_ME_RICH wrote:
Yeah - I probably confused the issue by describing my workstation console app as being expired (I only use it to see my other servers with licensed Red Gate copies on them).
My concerns are whether or not to upgrade the servers to 7.1, because there is not way that I see to update to 7.1 on my workstation (unless I can simply pull the directory from one of my servers, after I update them, and use it that way).
Is that possible?
I'll certainly defer to Marianne, being employed by the experts, but when you update the GUI, using Help ==> Check for Updates, and update it, it checks each registered server for the server components and tells you that there's an update available for that server. For stand-alone boxes (non-clustered) I usually update them using the GUI from a central server on the same domain, but for clusters you have to ship the server update file to each node and apply it manually.
Hope this helps.
BTW: I just had an issue upgrading the passive node to 7.1 and provoked a cluster failover! This is because the installer tried to bring the SQL Backup service online as a cluster resource on the PASSIVE Node - faux pas! I hope to have an answer on this issue soon, so you may want to watch it if you have clustered servers. Up to 7.1 I've never had an issue upgrading a passive node, so please beware. / comments
SQL_ME_RICH wrote:
Yeah - I probably confused the issue by describing my workstation console app as being expired (I only use it to see my other servers with licensed Red Gate copies on them).
M...
SQL_ME_RICH wrote:
If I am running an expired version of the SQL Backup tool on my local workstation, and I update my servers copies of SQL Backup to 7.1, am I going to have any issues managing/seeing/monitoring from my older, expired version of my workstationi console? I'm running either 7.0.5.1 or 7.0.6.2.
According to James Billings (Red Gate):
The GUI (the front end you interact with) can be installed anywhere you want (be it on each server, on your own PC, or somewhere else) and doesn't need to be licensed, so if you have, say, 10 DBA's they can all run the GUI on their own PC.
(See http://www.red-gate.com/MessageBoard/viewtopic.php?t=15106&highlight=cluster), so you should upgrade the UI immediately without issue... / comments
SQL_ME_RICH wrote:
If I am running an expired version of the SQL Backup tool on my local workstation, and I update my servers copies of SQL Backup to 7.1, am I going to have any issues managing/...
Vote for BOTH of these, I believe. http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1872217-auto-generated-insert-statement-is-buggy-with-comm http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1872709-moving-commas-from-end-to-start-is-always-bugg
THIRTY-FOUR VOTES BETWEEN THEM @ June 15, 2012.
Definitely a pain to work with! JAMES: This has been a Uservoice issue for 1 YEAR 1 MONTH and 20 DAYS. I don't think the posts are being read often enough... (IMO, only) / comments
Vote for BOTH of these, I believe.http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/1872217-auto-generated-insert-statement-is-buggy-with-commhttp://redgate.userv...
Per a very helpful response by Brian Donahue:
Sometimes clock skew can be prolonged by an overworked virtual machine. I did find this on Stack, maybe it explains your situation with SQL Monitor. http://serverfault.com/questions/28803/ ... ck-in-a-vm
Thanks,
Brian Donahue
Red Gate Product Support
My situation is that the Base Monitor is on a VM and monitors a physical active-passive cluster.
There is reference within the post cited above to a VMWare "tinker" setting that I don't profess to understand but looks like it should always be in place for my kind of architecture.
Hope this helps someone else... [image] / comments
Per a very helpful response by Brian Donahue:
Sometimes clock skew can be prolonged by an overworked virtual machine. I did find this on Stack, maybe it explains your situation with SQL Monitor. h...
Status: Ended Time raised: 5 Jun 2012 1:36 PM Time ended: 5 Jun 2012 9:41 PM
It appears to have taken about 2 hrs 20 minutes after the time was sync'd on the base and node2 for SQL Monitor to realize there was no longer an issue... Is this a bit excessive a lag?
Strangely, we didn't reset the active node until today but on the same day (Jun 5), for 15 minutes there was an apparent skew between the base and node1 of 17 seconds that lasted for only 15 minutes. Curious :? / comments
Status: Ended Time raised: 5 Jun 2012 1:36 PM Time ended: 5 Jun 2012 9:41 PM
It appears to have taken about 2 hrs 20 minutes after the time was sync'd on the base and node2 for SQL Monitor to rea...
I had the same problem!
Took a hammer to it and added the Service Account to the Local Admin Group and rebooted the server!
Works now 8) / comments
I had the same problem!
Took a hammer to it and added the Service Account to the Local Admin Group and rebooted the server!
Works now 8)
Perhaps I miscommunicated, Chris. I SHOULD have said that the rename was a TABLE rename, not a column or anything else rename.
There's no question of any data loss whatsoever.
This is a table rename, pure and simple. Custom migration scripts are in no way necessary and it would be a complete waste of my time to develop one.
The objective is ONLY "I want to rename the object in SVN having renamed it in the database".
Would that an sp_rename on a table were detected by SSC and handled as an SVN rename! Would an extended event facilitate this?
Perhaps in view of the revised information you could re-read the post and respond with something that may address the actual situation - that would help a lot. Thanks. / comments
Perhaps I miscommunicated, Chris. I SHOULD have said that the rename was a TABLE rename, not a column or anything else rename.
There's no question of any data loss whatsoever.
This is a table rena...
Thanks for the detailed explanation, Chris, it helps to understand the bigger picture on our end.
I used SQL Multi Script to deploy all the renames simultaneously across all our servers. Thankfully these are all audit-tables with only one of them being referenced by anything other than a data-change trigger. The only reason for renaming is due to SQL Prompt's inability to always show the schema in the suggestions list by default, and with identical table names, albeit with dbo and z_audit schema, I was tired of the wait for an enhancement and decided to make all the table names unique to reduce the noise in SQL Prompt.
I look forward to the continued improvements with SSC. Having endured 6 years of SQL Server with TFS not integrated into SSMS, SSC, despite some shortcomings, is now indispensable, non-invasive and, for our relatively small db-count and object-count site, very simple to operate. KISS works well for us!
Thanks again,
Regards,
Stephen / comments
Thanks for the detailed explanation, Chris, it helps to understand the bigger picture on our end.
I used SQL Multi Script to deploy all the renames simultaneously across all our servers. Thankfull...