 |
 |
| ActiveWin | Anonymous | Create a User | Reviews | News | Forums | Advertise | Career Portal | Users Online: 349 |
|
|
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
Active Network |
|
ActiveMac |
|
ActiveWin |
|
ActiveXbox |
|
Careers |
|
DirectX |
|
Downloads |
|
FAQs |
|
Interviews |
|
MS Games & Hardware |
|
Reviews |
|
Support Center |
|
TopTechTips |
|
Windows 2000 |
|
Windows Me |
|
Windows Server 2003 |
|
Windows Vista |
|
Windows XP |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
Apple/Mac |
|
Xbox/Xbox 360 |
|
News Search |
|
XML/RSS Newsfeeds |
|
Pocket PC Site |
|
|
|
|
|
|
|
FAQ's |
|
Windows Vista |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows Server 2003 |
|
Windows XP |
|
Windows 7 |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox 360 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
Latest Reviews |
|
Xbox/Games |
|
Fable 2 |
|
|
|
Applications |
|
Windows Server 2008 R2 |
|
Windows 7 |
|
IE 8 |
|
|
|
Hardware |
|
iPod Touch 32GB |
|
|
|
|
|
|
|
Latest Interviews |
|
Mike Swanson |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Advertise |
|
Affiliates |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
Sponsors:
Search Engine Optimisation
Search Engine Optimization
Search Engine Optimisation
Cheap Web Hosting
Webanalyse
online credit card processing
Lenovo Laptops
Text Links
Business Gifts
SEO Services
SEO
Search Engine Optimization
Quick House Sale
Electronic Medical Records
Practice Management
Windows 7 Themes
how to unlock iphone 3g
android on iphone
search engine optimisation
wooden gates
Network Software
 |
Microsoft Puts SQL Server in Line With Rivals on Backup Databases | |
|
||
| Time: 10:54 EST/15:54 GMT | News Source: ComputerWorld | Posted By: Robert Stein | ||
|
Microsoft last month announced that it would no longer charge Software Assurance customers for backup database servers, provided that the systems remain off unless the main database crashes or is corrupted and that they aren't used for processing on a regular basis. Previously, users had to pay a variable fee to install a backup SQL Server database for disaster recovery purposes, said Sunny Charlebois, a product manager in Microsoft's worldwide licensing and pricing group. | ||
|
Write Comment
Return to News |
Displaying Comments 1 through 11 of 11 |
The time now is
11:28:13 PM
ET.
Any comment problems? E-mail us |
| #1 By sodablue (5246 Posts) at 6/7/2004 12:04:02 PM |
|
I wonder how common this scenario is?
Most companies I have worked with use their backup recovery systems for pre-production testing. So that means they aren't turned off... however they aren't used for production either. Perhaps the journalist just doesn't understand technology. |
| #2 By theBixcuit (11 Posts) at 6/7/2004 12:14:39 PM |
| Isn't it necessary that a back-up server be up-to-date with the main database. How does it do this if it's off? |
| #3 By happyguy (387 Posts) at 6/7/2004 12:46:17 PM |
|
#1
There are other methods that can be used to achieve this. See below #2 "Isn't it necessary that a back-up server be up-to-date with the main database." Kind of. The way that my company is handling it is we use our EMC SAN to take BCVs of the environment at a regular schedule and replicate it across the WAN where it would wait for us to boot the failover target in the event of a failure. This post was edited by happyguy on Monday, June 07, 2004 at 12:48. |
| #4 By msucks (1716 Posts) at 6/7/2004 12:59:18 PM |
| That sounds kinda stupid. Maybe microsoft should take a look! |
| #5 By Parkker (1408 Posts) at 6/7/2004 2:28:57 PM |
|
It seems straightforward to me.
You image your server, apply the image to the cold server. You are allowed to update the cold server periodically to upgrade it or install SQL or OS patches. If you main server crashes, you either: Restore the backups from your backup respoitory to the cold server and apply the logs from the warm server (if the logs are ok) or restore the data from the warm server. You then boot up the cold server, set the name and IP address to the IP and name of the unwell server. http://download.microsoft.com/download/8/7/3/8733d036-92b0-4cb8-8912-3b6ab966b8b2/dr_brief.doc "a) The back-up server on which the software is run must be turned off except for: i. Limited disaster-recovery testing of and patch management on the software; or ii. In the case of an actual disaster. b) The disaster recovery copies of the software cannot be installed on a server in the same cluster as the production server. c) In the case of an actual disaster, the software may not be run simultaneously on both the disaster recovery back-up server and the production server, except while the production server is being recovered. When the production server is back online, use of the software under the disaster recovery licenses is again subject to the conditions described here. d) Complimentary disaster recovery licenses are non-perpetual, and expire upon expiration or termination of the Software Assurance for the corresponding qualifying license or related CALs. If Software Assurance coverage is discontinued, any copy of the software installed on the cold back-up server under a complimentary disaster recovery license must be uninstalled. e) The version, edition and type of the complimentary disaster recovery license and the underlying license for the qualifying server software are identical (for example, if the underlying license for the qualifying server software is a Microsoft® SQL Server 2000 Standard processor license, then the complimentary DR license is likewise a Microsoft SQL Server 2000 Standard processor license)." |
| #6 By Mr. Dee (3459 Posts) at 6/7/2004 7:03:58 PM |
| Well, its better to give essential add ons since Yukon is taking forever! |
| #7 By diaphanein (323 Posts) at 6/7/2004 7:29:48 PM |
|
#6, I'm glad MS is taking their time, rather taking the approach of IBM and shipping despite readiness (or lack thereof). I'm absoluting sick of dealing with IBM's crapware that they call DB2. We spent over 6 months testing, filing PMRs, applying fixpacks and hotfixes to DB2 Connect v8 before we even considered a rollout into production on a very limitted basis. We lose support for v7 this fall, but v8 isn't ready or stable enough to take its place. Way to go, IBM!
Realistically, more often than not, deadlines are a joke in the computer world. You should be thankful that MS has done the honorable thing and said, "Hey, we're not ready," than saying, "Here you go. Don't breath, hop on one foot while typing with one hand and hope it works." |
| #8 By Mr. Dee (3459 Posts) at 6/7/2004 8:09:31 PM |
| #7, Amazon.com runs DB2. |
| #9 By diaphanein (323 Posts) at 6/8/2004 12:58:16 AM |
|
#8, So? The database itself is pretty solid....but in a distributed environment, DB2 connect is a piece of crap. Unreliable at best. At worst, completely unusable. And their marketing claims that you can develop on distributed and then deploy on os390/zOS? Complete and utter bull. Unless, you keep in mind that the mainframe edition implements a subset of the features as the distributed platforms (and supports things the distributed side doesn't).
In all these years, they still haven't gotten some basic things right under windows. NTLM authentication is broke under v8. Not missing....BROKE. As in, no such luck. Try again another fixpack later. Oh, and OleDb? Yeah....prior to v8 FP 4a, try and get SQL State and the native error number from an error object....They're not populated. Oh, and try and pass a date in a parameterized query...won't work - it passes it as a timestamp and inevitably fails due to a datatype conversion problem. These are basic things that are broke. SOME of these are fix in later fixpacks of v8. Some of these are either still broke in v7 (fp 12 now), or were REintroduced. IBM's QA seems to be shot. Not to mention their marketing lies. The initial docs for v8 said that all you needed was the IBM .Net managed provider. What they failed to mention is that you also need DB2 Connect Gateway (the documentation led developers to believe they could connect directly to the mainframe, which turned out to be a complete an utter fabrication). Another good one is that under v8, suppose you install the DB2 Connect runtime. They, you goto apply a fixpack. Unlike before, there's a seperate fixpack for each and every version of connect and UDB. If you pick the wrong fixpack....it doesn't complain, it just does it. So, you can go from db2 connect runtime to db2 connect unlimited edition just by accidentally applying the wrong fixpack - with absolutely no warning. BUT, of course it won't run mysteriously, because you're missing the license file. Oh - and why the hell can't they install that by default? ITS ON THE SAME CD AS THE SETUP. But no, you have to go in manually, copy the file over (which isn't like its unique like a CD key) and run db2licm on it. Annoying and rediculous. Is this enough to make my point? |
| #10 By sodablue (5246 Posts) at 6/8/2004 12:14:05 PM |
| diaphanein - Wow, that's worse than our experience with Oracle. |
| #11 By Mr. Dee (3459 Posts) at 7/2/2004 11:13:51 PM |
| I think Oracle is a good database, only problem is its still darn expensive, although I have heard that they have dropped the price in the MS SQL ranges. |
|
Write Comment
Return to News |
Displaying Comments 1 through 11 of 11 |
The time now is
11:28:13 PM
ET.
Any comment problems? E-mail us |
