I would like to set up a new SQL server on a completely different box in a different location in the company (perhaps even offsite). I want this new server to be a mirror of the original SQL server, such that when data in the original server is updated the data in the new one is also updated etc.... I would like to do this for security reasons, such that if the original server goes up in flames, I can recover all the data and quickly switch to the new server. I have only ever had to deal with one SQL server at once before, so what I want to know is: Is this the best way to ensure against catastrophic failure of the server. What do I need to read up on to achieve this. Thanks.
mirror
11 posts
• Page 1 of 1
- MS OFFICE OUTLOOK
- WINDOWS VISTA
- FLASH
- Windows
- Exchange 2000
- c++ moderated
- Exchange 2000
- c++ builder
- MS WORD
- Computer architecture
Jump to:
- 1. Problem with this query
I'm trying to write a query that will CREATE and UPDATE the same record if the RECORD meets some criteria. This is time keepinig system. When an employee clocks in, a records will be CREATED. When he/she clocks OUT, the QUERY is suppose to LOCATE the "last" record and UPDATES the TimeOut field. Somehow, my query can create the RECORD, UPDATE punch OUT, but i cannot ADD a NEW record. Please help. Thanks. DECLARE @NewPunch int SET @NewPunch = (Select Count(*) from Punch where EmpNo = 101 and TimeIN > 0); IF (@NewPunch > 0) begin UPDATE PUNCH SET TimeOUT = GetDate() WHERE EmpNo = 101 and TimeOUT is NULL end else begin INSERT INTO PUNCH(EmpNo, TimeIN, Booth, WorkDate) VALUES (101, GetDate(), 1, GetDate()) end - 2. SQL Server 2005
Anybody know how much the SQL 2005 upgrade will cost, or where I could get a price? Thanks, -Ben - 3. Multiple File Groups
Hi, I just inherited an Active/Passive SQL 2000 cluster from a previous DBA. And I discovered that one of the database has about 5 file groups pointing to a different drives. How can I find out which tables are pointing to different file groups or what indexes (if any) point there? Thank you, T.
Next
mirror
by JosephByrns » Thu, 23 Mar 2006 22:31:47 GMT
RE: mirror
by Sm9obiBCZWxs » Thu, 23 Mar 2006 22:46:29 GMT
Hi There are different options available depending on which version of SQL Server you are running and what your system configuration is. With SQL 7 - 2005 you can use log shipping or replication. SQL 2005 has database mirroring. There are also options that require specific hardware such as failover clustering and SAN replication. You may want to check out http://www.**--****.com/ an introduction. John
RE: mirror
by QW5keVA » Thu, 23 Mar 2006 23:11:27 GMT
Bear in mind that there is a Microsoft article on Mirroring that stipulates that they do not recommend database mirroring in a production environment, and should only be used in development and test environments. Please see this article. http://www.**--****.com/ -- AndyP, Sr. Database Administrator, MCDBA 2003
Re: mirror
by JosephByrns » Thu, 23 Mar 2006 23:50:45 GMT
Thank you both for the info, this is on SQL Server 2000, so I guess mirriring doesn't apply here.
Re: mirror
by JosephByrns » Fri, 24 Mar 2006 01:56:53 GMT
OK, it looks like log shipping will do what I want, unfortunately it appears that Log Shipping is only available to SQL 2000 Enterprise (I have Professional), can you confirm this is true? Will I require enterprise for the replication approach? Thanks.
Re: mirror
by Tibor Karaszi » Fri, 24 Mar 2006 18:49:56 GMT
Log shipping is only backup and restore. Can be done with any edition. But if you don't have EE, you have to write your own jobs (or Google if someone has shared). -- Tibor Karaszi, SQL Server MVP http://www.**--****.com/ http://www.**--****.com/
Re: mirror
by JosephByrns » Fri, 24 Mar 2006 19:21:13 GMT
reat, thanks, I'll look into it.
"Tibor Karaszi" < XXXX@XXXXX.COM > wrote in
message news:% XXXX@XXXXX.COM ...
"Tibor Karaszi" < XXXX@XXXXX.COM > wrote in
message news:% XXXX@XXXXX.COM ...
Re: mirror
by clxowen » Mon, 22 May 2006 18:10:56 GMT
his is a multi-part message in MIME format.
This is an outdated article.
Since Microsoft didn't strictly test data mirror on SQL 2005 RTM, so, Microsoft doesn't recommend you carry out mirroring in a product environment.
But now, as you know, SQL 2005 SP1 has been release on 18th, April. We can complete implement
it in your product server.
"AndyP" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Bear in mind that there is a Microsoft article on Mirroring that stipulates
that they do not recommend database mirroring in a production environment,
and should only be used in development and test environments.
Please see this article.
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
--
AndyP,
Sr. Database Administrator,
MCDBA 2003
"John Bell" wrote:
> Hi
>
> There are different options available depending on which version of SQL
> Server you are running and what your system configuration is. With SQL 7 -
> 2005 you can use log shipping or replication. SQL 2005 has database
> mirroring. There are also options that require specific hardware such as
> failover clustering and SAN replication.
>
> You may want to check out
> http://www.microsoft.com/sql/technologies/highavailability/default.mspx for
> an introduction.
>
> John
>
> "JosephByrns" wrote:
>
> > I would like to set up a new SQL server on a completely different box in a
> > different location in the company (perhaps even offsite). I want this new
> > server to be a mirror of the original SQL server, such that when data in the
> > original server is updated the data in the new one is also updated etc....
> > I would like to do this for security reasons, such that if the original
> > server goes up in flames, I can recover all the data and quickly switch to
> > the new server.
> >
> > I have only ever had to deal with one SQL server at once before, so what I
> > want to know is:
> >
> > Is this the best way to ensure against catastrophic failure of the server.
> > What do I need to read up on to achieve this.
> >
> > Thanks.
> >
> >
> >
!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN>> <
<
<
<
<
<This is an outdated
article< <Since Microsoft didn't strictly
test data mirror on SQL 2005 RTM, so, Microsoft doesn't recommend you carry out
mirroring in a product environment< <But now, as you know, SQL 2005 SP1
has been release on 18th, April. We can complete implemen< <it in your product
server< < <
<
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px solid; MARGIN-RIGHT: 0px
This is an outdated article.
Since Microsoft didn't strictly test data mirror on SQL 2005 RTM, so, Microsoft doesn't recommend you carry out mirroring in a product environment.
But now, as you know, SQL 2005 SP1 has been release on 18th, April. We can complete implement
it in your product server.
"AndyP" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Bear in mind that there is a Microsoft article on Mirroring that stipulates
that they do not recommend database mirroring in a production environment,
and should only be used in development and test environments.
Please see this article.
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
--
AndyP,
Sr. Database Administrator,
MCDBA 2003
"John Bell" wrote:
> Hi
>
> There are different options available depending on which version of SQL
> Server you are running and what your system configuration is. With SQL 7 -
> 2005 you can use log shipping or replication. SQL 2005 has database
> mirroring. There are also options that require specific hardware such as
> failover clustering and SAN replication.
>
> You may want to check out
> http://www.microsoft.com/sql/technologies/highavailability/default.mspx for
> an introduction.
>
> John
>
> "JosephByrns" wrote:
>
> > I would like to set up a new SQL server on a completely different box in a
> > different location in the company (perhaps even offsite). I want this new
> > server to be a mirror of the original SQL server, such that when data in the
> > original server is updated the data in the new one is also updated etc....
> > I would like to do this for security reasons, such that if the original
> > server goes up in flames, I can recover all the data and quickly switch to
> > the new server.
> >
> > I have only ever had to deal with one SQL server at once before, so what I
> > want to know is:
> >
> > Is this the best way to ensure against catastrophic failure of the server.
> > What do I need to read up on to achieve this.
> >
> > Thanks.
> >
> >
> >
!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN>> <
article< <
test data mirror on SQL 2005 RTM, so, Microsoft doesn't recommend you carry out
mirroring in a product environment< <
has been release on 18th, April. We can complete implemen< <
server< <
Re: mirror
by Sm9obiBCZWxs » Mon, 22 May 2006 18:49:01 GMT
i
I believe there is a method of log shipping in the resource kit and there
has also been several articles on rolling your own log shipping in SQL Server
Magazine e.g.
http://www.sqlmag.com/Article/ArticleID/15805/Log_Shipping_with_SQL_Server_2000.html
John
"JosephByrns" wrote:
I believe there is a method of log shipping in the resource kit and there
has also been several articles on rolling your own log shipping in SQL Server
Magazine e.g.
http://www.sqlmag.com/Article/ArticleID/15805/Log_Shipping_with_SQL_Server_2000.html
John
"JosephByrns" wrote:
Similar Threads:
1.Alert Mirroring State changes from Witness Mirroring Monitor?
I have 2005 mirroring working fine with a 3rd witness server. but I don't see how to alert from Mirroring Monitor running on the witness. A technet article goes into great detail about sys.sp_dbmmonitoraddmonitoring and other related stored procedures but they seem to run off a hidden system table for the monitored database that is not being created on my witness - presumably because Mirroring Monitor is being run on a witness that does not have a copy of the monitored database. So how do I request mirroring states on a witness machine so I can alert from the Witness when states change? Thanks Bill
I have posted this once before but I cannot find the thread for some reason. I have a client that I am going to be doing some colo hosting for. He has two brand new servers. He has not bought any operating systems as of yet and will also need SQL Server. The only thing these will be used for is housing SQL databases for scheduled web data collection and reporting. I have read until I am almost cross-eyed but still cannot figure out if I should go with clustering or just do database mirroring within SQL. I have another server which could be used as the witness for mirroring, as well as the file server for external storage for a cluster. Can anyone lead me in the best direction? Let me know if you have more questions. Thanks, Marty
3.Data Mirroring sql server user account haven't use when failover to mirroring database
I setup a mirroring database, have principal (host A), mirroring (host B), withness (host C) i create a user account and login account "usera" can login can retieve data in principal server (host A) when occur failover to host B, host B become principal, but i can connect host B using "usera", i saw host B have a user account "usera" in host B, but haven't the login account, then i create login account "usera", but the "usera" login account only can login only, can't access database, anyone can help, Many many thanks.
4.Persistent mirroring witness disconnected probem on mirror
Hi, I'm running a syncornized mirroring setup using a witness on our LAN. Since we don't use a domain controller, we use certificates for outbound and inbound mirroring connections. We're using sql server 2005 SP1 standard edititon on all machines. The principal and mirror have only the partner role The witness has only the witness role After exeucting 'alter database set witness' on server1, the mirror monitor shows that server1, the pricnipal, is connected to the witness, but server2, the mirror, is disconnected from the witness. When performing a manual failover (alter databsase set partner failover), server2, now the principal, is still disconnected from the witness. I've eliminated the possibility that server2 and the witness have a connection problem, by dropping the witness from server1 when server1 was the principal, and adding it to server2, when server2 was the principal. Then, server1 is the one with the disconnected problem. When executing the set witness command on a mirror, I get an error that it can only be done on the principal machine. Any ideas? Thanks, Ronen
5.Sync mirroring - Ack failure from mirror DOES or DOES not cause rb
6. Sync mirroring - Ack failure from mirror DOES or DOES not caus
7. Backup a mirrored Database ( on the mirror, not on the principal )
8. Database Mirroring not synching till I open Mirroring Monitor
11 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 59 guest