Geocacher

|
|
| |
|
Geocacher

|
Looks like it's been fixed.
|
| |
|
Geocacher

|
That sounds right. I guess "fix" wasn't really the best word to use. They had a workaround until they could actually get it fixed.
|
| |
|
Rinocacher

 |
quote: Originally posted by AllenLacy: I believe Jeremy said the computer that runs the read-only copy of the database which is used by the PQ generator had problems so they brought up another computer and placed a copy of the database on it.
The *computer* had problems that prevented it from having the most recent data? Uh, ok. Trout, Denmark, and olefactory impoliteness. Regardless, as long as it's working correclty now.
|
| |
| Posts: 948 | Location: Marietta, GA | Registered: December 15, 2002 |    |
|
Neutiquam erro.

|
Well the message said quote: We had a database failure in one of the secondary (Read-only) databases.
So it wasn't the computer, but the actual secondary database. I could say something about using M$ database software in a high demand environment but I won't. -----
|
| |
| Posts: 2411 | Location: NE Corner of Georgia | Registered: November 09, 2002 |    |
|
Geocacher

|
quote: I could say something about using M$ database software in a high demand environment but I won't.
I've worked in environments with Oracle, Sybase, iSQL, and MSSQL in high-demand production environments and all have gone down at least once that required multiple-hour recovery and usually with vendor help. Usually MSSQL installs failing are the same as with the OS, they are just thrown together by people who don't know what they are doing (usually because MSSQL is the lowest cost). My current job is at a place that has over 150 servers housing a few thousands MSSQL databases and hopefully they will all continue to work well (or I might lose my job). reepicheep
|
| |
| Posts: 1437 | Location: Dacula, GA, USA | Registered: January 10, 2003 |    |
|
Neutiquam erro.

|
Well the good news was the primary database was ok; the bad news was the secondary database was messed up and they didn't know it until the users complained, repeatedly. One thing that appears to be a weakness of MS SQL Server is that as far as I can tell it can’t do hot backups, i.e. backup the database while it is in use(1). Jeremy mentioned they shut the primary database down once a week, to back it up to tape and once a month to re-index. 15 years ago in a shop using Oracle we had to stay up 2 nines (99% of the time), so we did hot backups to tape. My current position our goal is to keep our DB2 database up three nines (99.9%) which allows us to be down 43 minutes a month. So we do hot backups to tape and keep a redundant copy on a different box. I have talked with the DBA of a telecommunications company using Oracle and their goal was 5 nines (99.999%) which allows them to be down 5 minutes and 15 seconds a year. So they do hot backups and have 2 redundant copies with automatic switch over. Never seen a MS SQL Server that would stay up that much. (1) I have seen 3rd party software which allows hot backups of MS SQL Server. -----
|
| |
| Posts: 2411 | Location: NE Corner of Georgia | Registered: November 09, 2002 |    |
|