Comments
Sort by recent activity
I've been following this thread with interest, and am curious to know if you are planning on doing something in SQL Backup that will address this when Microsoft stops writing any further service packs and updates for SQL Server 2005?
Microsoft's product lifecycle typically for SQL Server has been 10 years of support (Mainstream, Extended, ect...). That puts SQL Server 2005 really close to the end of it's lifecycle, so I am just curious if at that point, could there potentially be a fix for this particular issue that Red Gate could handle on it's own? / comments
I've been following this thread with interest, and am curious to know if you are planning on doing something in SQL Backup that will address this when Microsoft stops writing any further service pa...
Yeah - unfortunately, that won't work for this particular scenario, but thank you for the information! / comments
Yeah - unfortunately, that won't work for this particular scenario, but thank you for the information!
Thanks Marianne - I got it resolved.
SQL_ME_RICH / comments
Thanks Marianne - I got it resolved.
SQL_ME_RICH
PDinCA wrote:
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...
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? / comments
PDinCA wrote:
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...
Marianne wrote:
Hi,
I'm afraid we cannot guarantee forwards-compatibility of the user interface. We support backwards-compatibility, meaning that you can run a later version of the UI with an older version of the server components, but not the other way around.
Are you having any problems upgrading the UI to 7.1?
Cheers,
Marianne
Hi Marianne - another user brought up a good point, in that I should be able to run the app from my workstation (even if it is expired - and really that wasn't the point - sorry for the confusion on that). I guess what I need to know is if I uninstall my current copy of Backup 7, update my servers that are currently licensed to 7.1, and then pull one of their folders over to my workstation, will that work? / comments
Marianne wrote:
Hi,
I'm afraid we cannot guarantee forwards-compatibility of the user interface. We support backwards-compatibility, meaning that you can run a later version of the UI with an ol...
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. / comments
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...
OK - it definitely is a configuration issue on our end. 1 of the 3 servers is in our corporate domain while the other 2 are not. This has actually opened up a whole other can of worms, so just know that I am working fine again. / comments
OK - it definitely is a configuration issue on our end. 1 of the 3 servers is in our corporate domain while the other 2 are not. This has actually opened up a whole other can of worms, so just kn...
I have to tell you though - this kind of bothers me. I have 2 other instances that I have in my copy here locally, along with this one (that I now have to access via IP address). The 2 others are access the instances with no problem, using the Server names. If it were a DNS problem - I would think that the effects from such an issue would be seen elsewhere with other things, but nothing else is amiss here.
Any ideas on why this one server would not resolve my server name, but has no issues with the other 2? Have you had an issue like this in the past? / comments
I have to tell you though - this kind of bothers me. I have 2 other instances that I have in my copy here locally, along with this one (that I now have to access via IP address). The 2 others are a...
Nothing about the connection string has changed since it first worked. No port is being specified when I specify the server name (and I have done it both by IP Address and Machine Name in the past with success in either case), but right now it is using the machine name, and is not working. I tried switching it over to just the IP address, but have the same results.
EDIT: I now have it working via IP address with SQL Authentication. This did not happen before. Let me try this for a bit, and see if I can determine why it is having trouble with the machine name. If I wind up having troiuble still - I will post back. / comments
Nothing about the connection string has changed since it first worked. No port is being specified when I specify the server name (and I have done it both by IP Address and Machine Name in the past...
Nothing is on my desktop, but if what you are asking me is if I go into SSMS and connect to that database instance via my local copy of SSMS, does it connect? The answer is yes it does (and I am using SQL Auth both for Red Gate and the SSMS connection to it). / comments
Nothing is on my desktop, but if what you are asking me is if I go into SSMS and connect to that database instance via my local copy of SSMS, does it connect? The answer is yes it does (and I am u...