It is my understanding that this Active Directory account takes on the
role(s) of SQL's BuiltIn Administrator in a clustered environment.
Should the ClusterService Log On account password be reset in AD, without
reseting in the properties tab for the service on the physical nodes cluster
fail overs can still occur because the ClusterService has already been
started. BUT, what activity in SQL2000 could the AD account be doing on
behalf of the SQL BuiltIn Administrator account that would affect the
cluster and initiate a failover if it could not authenticate on the Domain?
Dave
That is not right. By default (God, I hate Microsoft's defaults), the
Cluster Service MUST BE a member of the Local Administrators group on each
cluster node, by which it gains access to the SQL Server installations
through the default BUILTIN\Administrators membership to the SQL Server
system admin default server role.
If you follow the security best practices, and you should, you will remove
the BUILTIN\Administrators group for the installation; however, the Cluster
Service account will still need access to run the resource monitor "Is
Alive" check, which, in the case for the SQL Server resource, is nothing but
the SELECT @.@.SERVERNAME query; thus, the Cluster Service account merely
needs access to the installation, but no special rights beyond this, as the
guest database user in the master database has permissions to execute this
query.
Sincerely,
Anthony Thomas
"David Currie" <decurrie@.rogers.com> wrote in message
news:%23aT3qmQBHHA.204@.TK2MSFTNGP04.phx.gbl...
> It is my understanding that this Active Directory account takes on the
> role(s) of SQL's BuiltIn Administrator in a clustered environment.
> Should the ClusterService Log On account password be reset in AD, without
> reseting in the properties tab for the service on the physical nodes
cluster
> fail overs can still occur because the ClusterService has already been
> started. BUT, what activity in SQL2000 could the AD account be doing on
> behalf of the SQL BuiltIn Administrator account that would affect the
> cluster and initiate a failover if it could not authenticate on the
Domain?
> Dave
>
Showing posts with label log. Show all posts
Showing posts with label log. Show all posts
Saturday, February 25, 2012
Friday, February 24, 2012
Clusters and Log Shipping
Does anyone know of any issues with using Active/Passive or Active/Active clusters and log shipping. Will log shipping still work if a failover occurs?
Thanks
Yes, log shipping still works after a cluster failover. A failover in a cluster is basically the same as restarting your SQL Service. Assuming you have log shipping configured correctly (i.e. using the virtual instance name, which would be the case if you configured log shipping using the built-in wizards/plans), log shipping will pick up where it left off before the failover occured (i.e. the next time the t-log is backed up, it will be shipped to your shared log location for application to the standby server).
HTH
|||Setting up log-shipping between two clusters gets a little more intricate because you have to establish the file shares log-shipping needs and although the shared disk fails over, the shares have to be setup in advance, and the node has to be the active node in order to setup the "shared disk" shares.
Clusters and Log Shipping
Does anyone know of any issues with using Active/Passive or Active/Active clusters and log shipping. Will log shipping still work if a failover occurs?
Thanks
Yes, log shipping still works after a cluster failover. A failover in a cluster is basically the same as restarting your SQL Service. Assuming you have log shipping configured correctly (i.e. using the virtual instance name, which would be the case if you configured log shipping using the built-in wizards/plans), log shipping will pick up where it left off before the failover occured (i.e. the next time the t-log is backed up, it will be shipped to your shared log location for application to the standby server).
HTH
|||Setting up log-shipping between two clusters gets a little more intricate because you have to establish the file shares log-shipping needs and although the shared disk fails over, the shares have to be setup in advance, and the node has to be the active node in order to setup the "shared disk" shares.
Clustering Vs. Log Shipping
Hi All,
Is anyone can tell me the difference between log shipping and clustering? I look at it and I think that this is the same thing as they use two different servers.
TIA
No they are not even close, Clustering is hardware operation that let your application failover to a live standby through a configuration called heart beat while Log Shipping let you within a few minutes create a new running version of your database. If you are in SQL Server 2005 it comes with something called database Mirroring as of service pack 1 it is almost but not quite Clustering because the change over is smoother than Log Shipping so almost like hardware Clustering. Run a search for database Mirroring in SQL Server BOL(books online). Hope this helps.|||Thank you Caddre.
But what make me confused is that they both have 2 different server. So, in terms of cost they are almost the same. Then, the only difference that I see is the time delay. Clustering would be faster to recover than Log Shipping. Also, Log Shipping only copy the transaction log (what is that means?)
TIA
|||Not quite because Cluster boxes are very expensive but you can configure any box to do Log Shipping, because the later is just a dedicated Backup/Restore operation, while the former is a smooth invisible failover through Active/Passive or Active/Active configuration based on the hardware vendor's provided features in the Cluster box. So Log Shipping could be cheap available to most users who can afford the extra box while Cluster is expensive hardware and may require extra hardware components beyound the Cluster box to use and skilled System/Database Admin. Hope this helps.
http://msdn2.microsoft.com/en-us/library/ms188698.aspx
|||Thank you Gift,
I am clear now.
|||
ronnyr:
Thank you Gift,
I am clear now.
I am glad I could help.
Clustering Set up
I am thining about either setting up Cluseting on SQL
Server or follow log shipping. Does anyone has any
recommendation as to which one should be chosen? Also,
can someone direct me to a proper location where there is
step by step instruction on how to set up Clustering/ Log
Shipping.
Also, Is it easy to manager Clustering or LS or it's a
nightmare.
Does anyone know if it is easier to manager Clustering/ LS
in SQL 2005. I may wait for another few months if it is
more stable and easier to manage in the new release.
Any help will be highly appreciated.
-Nitin
Books On Line has a lot of information on Clustering and Log shipping setup.
What are you trying to achieve with clustering / log shipping?
High availability? Reporting Server?
As soon as you go clustering, you need expensive hardware and shared storage
(SAN), Enterprise Editions of the OS and SQL.
Log shipping is easier as you can use existing hardware that you may have.
Yukon does make it easier to setup and manage, but you still need to know
what you are doing if you cluster as SQL uses the OS's clustering services
to run on.
--
Mike Epprecht, Microsoft SQL Server MVP
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nitin Rana" <Nitin_Rana@.Ibi.com> wrote in message
news:23d701c47022$776b82b0$a601280a@.phx.gbl...
> I am thining about either setting up Cluseting on SQL
> Server or follow log shipping. Does anyone has any
> recommendation as to which one should be chosen? Also,
> can someone direct me to a proper location where there is
> step by step instruction on how to set up Clustering/ Log
> Shipping.
> Also, Is it easy to manager Clustering or LS or it's a
> nightmare.
> Does anyone know if it is easier to manager Clustering/ LS
> in SQL 2005. I may wait for another few months if it is
> more stable and easier to manage in the new release.
> Any help will be highly appreciated.
> -Nitin
|||Nitin,
Both SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping are disaster recovery options. Based on your requirements, you will need to decide what option best suits you. It is not uncommon to
see clients using SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping together also. It just depends on their needs.
Here is a Microsoft Knowledge Base article that explains the various disaster recovery options
Disaster recovery options for Microsoft SQL Server
http://support.microsoft.com/?kbid=822400
After reviewing this article, you may have many qs on SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping. Here are some links that you may find useful
Microsoft Whitepaper - SQL Server 2000 Failover Clustering >>>>>>>> Has Step By Step Instructions on installing SQL Server 2000 Failover Cluster <<<<<<<<<<
http://www.microsoft.com/technet/pro.../failclus.mspx
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
If you are considering Clustering then you will need to have a Certified Cluster solution.
How to locate qualified cluster solutions for Windows
http://support.microsoft.com/?id=828262
Microsoft's Cluster support policy is explained in these articles: Please read these carefully for the official support policy of
Cluster (General): http://support.microsoft.com/default...b;en-us;309395
Cluster (SQL): http://support.microsoft.com/default...b;en-us;327518
The following links will give you more information for Log Shipping
INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?kbid=314515
Whitepaper - SQL Server 2000 How To Setup Log Shipping >>>>>>>> Has Step By Step Instructions on installing SQL Server 2000 Log Shipping <<<<<<<<<<
http://www.microsoft.com/downloads/r...rch&ordinal=31
SQL Server 2000 Failover Clustering and Log Shipping both are very stable and fairly simple to manage (-- that will actually depend on the DBAs experience as these are advanced features). Definitely,
SQLServer 2005 will have more features as compared to SQL Server 2000. There will be more disaster recovery options -- for ex. Database Mirroring. For more information on SQL Server 2005, please visit
http://www.microsoft.com/sql/yukon/p...fo/default.asp
Here you will find lots of whitepapers and information on SQL Server 2005.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||For Top 30 Features of SQL Server "Yukon", visit
http://www.microsoft.com/sql/yukon/p...30features.asp
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
This information really looks like it contains lots of
useful information. I will go over this information and
would like to set it up. Thanks and your help is really
appreciated.
-Nitin
>--Original Message--
>Nitin,
>Both SQL Server 2000 Failover Clustering and SQL Server
2000 Log Shipping are disaster recovery options. Based on
your requirements, you will need to decide what option
best suits you. It is not uncommon to
>see clients using SQL Server 2000 Failover Clustering and
SQL Server 2000 Log Shipping together also. It just
depends on their needs.
>Here is a Microsoft Knowledge Base article that explains
the various disaster recovery options
>Disaster recovery options for Microsoft SQL Server
>http://support.microsoft.com/?kbid=822400
>After reviewing this article, you may have many qs on SQL
Server 2000 Failover Clustering and SQL Server 2000 Log
Shipping. Here are some links that you may find useful
>Microsoft Whitepaper - SQL Server 2000 Failover
Clustering >>>>>>>> Has Step By Step Instructions on
installing SQL Server 2000 Failover Cluster <<<<<<<<<<
>http://www.microsoft.com/technet/pro.../sql/2000/main
tain/failclus.mspx
>Microsoft SQL Server 2000 High Availability Series
>http://www.microsoft.com/technet/pro.../sql/2000/depl
oy/sqlhalp.mspx
>If you are considering Clustering then you will need to
have a Certified Cluster solution.
>How to locate qualified cluster solutions for Windows
>http://support.microsoft.com/?id=828262
>Microsoft's Cluster support policy is explained in these
articles: Please read these carefully for the official
support policy of
>Cluster (General):
http://support.microsoft.com/default.aspx?scid=kb;en-
us;309395
>Cluster (SQL): http://support.microsoft.com/default.aspx?
scid=kb;en-us;327518
>The following links will give you more information for
Log Shipping
>INF: Frequently Asked Questions - SQL Server 2000 - Log
Shipping[vbcol=seagreen]
>http://support.microsoft.com/?kbid=314515
>Whitepaper - SQL Server 2000 How To Setup Log Shipping
Server 2000 Log Shipping <<<<<<<<<<
>http://www.microsoft.com/downloads/release.asp?
ReleaseID=30186&area=search&ordinal=31
>SQL Server 2000 Failover Clustering and Log Shipping both
are very stable and fairly simple to manage (-- that will
actually depend on the DBAs experience as these are
advanced features). Definitely,
>SQLServer 2005 will have more features as compared to SQL
Server 2000. There will be more disaster recovery options -
- for ex. Database Mirroring. For more information on SQL
Server 2005, please visit
>http://www.microsoft.com/sql/yukon/p...fo/default.asp
>Here you will find lots of whitepapers and information on
SQL Server 2005.
>HTH,
>Best Regards,
>Uttam Parui
>Microsoft Corporation
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Are you secure? For information about the Strategic
Technology Protection Program and to order your FREE
Security Tool Kit, please visit
http://www.microsoft.com/security.
>Microsoft highly recommends that users with Internet
access update their Microsoft software to better protect
against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites:
>http://www.microsoft.com/protect
>http://www.microsoft.com/security/guidance/default.mspx
>
>.
>
|||You can also check out the book SQL Server 2000 High
Availability from MS Press as well ... it goes into more
depth and has Windows Server 2003 content.
Server or follow log shipping. Does anyone has any
recommendation as to which one should be chosen? Also,
can someone direct me to a proper location where there is
step by step instruction on how to set up Clustering/ Log
Shipping.
Also, Is it easy to manager Clustering or LS or it's a
nightmare.
Does anyone know if it is easier to manager Clustering/ LS
in SQL 2005. I may wait for another few months if it is
more stable and easier to manage in the new release.
Any help will be highly appreciated.
-Nitin
Books On Line has a lot of information on Clustering and Log shipping setup.
What are you trying to achieve with clustering / log shipping?
High availability? Reporting Server?
As soon as you go clustering, you need expensive hardware and shared storage
(SAN), Enterprise Editions of the OS and SQL.
Log shipping is easier as you can use existing hardware that you may have.
Yukon does make it easier to setup and manage, but you still need to know
what you are doing if you cluster as SQL uses the OS's clustering services
to run on.
--
Mike Epprecht, Microsoft SQL Server MVP
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nitin Rana" <Nitin_Rana@.Ibi.com> wrote in message
news:23d701c47022$776b82b0$a601280a@.phx.gbl...
> I am thining about either setting up Cluseting on SQL
> Server or follow log shipping. Does anyone has any
> recommendation as to which one should be chosen? Also,
> can someone direct me to a proper location where there is
> step by step instruction on how to set up Clustering/ Log
> Shipping.
> Also, Is it easy to manager Clustering or LS or it's a
> nightmare.
> Does anyone know if it is easier to manager Clustering/ LS
> in SQL 2005. I may wait for another few months if it is
> more stable and easier to manage in the new release.
> Any help will be highly appreciated.
> -Nitin
|||Nitin,
Both SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping are disaster recovery options. Based on your requirements, you will need to decide what option best suits you. It is not uncommon to
see clients using SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping together also. It just depends on their needs.
Here is a Microsoft Knowledge Base article that explains the various disaster recovery options
Disaster recovery options for Microsoft SQL Server
http://support.microsoft.com/?kbid=822400
After reviewing this article, you may have many qs on SQL Server 2000 Failover Clustering and SQL Server 2000 Log Shipping. Here are some links that you may find useful
Microsoft Whitepaper - SQL Server 2000 Failover Clustering >>>>>>>> Has Step By Step Instructions on installing SQL Server 2000 Failover Cluster <<<<<<<<<<
http://www.microsoft.com/technet/pro.../failclus.mspx
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
If you are considering Clustering then you will need to have a Certified Cluster solution.
How to locate qualified cluster solutions for Windows
http://support.microsoft.com/?id=828262
Microsoft's Cluster support policy is explained in these articles: Please read these carefully for the official support policy of
Cluster (General): http://support.microsoft.com/default...b;en-us;309395
Cluster (SQL): http://support.microsoft.com/default...b;en-us;327518
The following links will give you more information for Log Shipping
INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?kbid=314515
Whitepaper - SQL Server 2000 How To Setup Log Shipping >>>>>>>> Has Step By Step Instructions on installing SQL Server 2000 Log Shipping <<<<<<<<<<
http://www.microsoft.com/downloads/r...rch&ordinal=31
SQL Server 2000 Failover Clustering and Log Shipping both are very stable and fairly simple to manage (-- that will actually depend on the DBAs experience as these are advanced features). Definitely,
SQLServer 2005 will have more features as compared to SQL Server 2000. There will be more disaster recovery options -- for ex. Database Mirroring. For more information on SQL Server 2005, please visit
http://www.microsoft.com/sql/yukon/p...fo/default.asp
Here you will find lots of whitepapers and information on SQL Server 2005.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||For Top 30 Features of SQL Server "Yukon", visit
http://www.microsoft.com/sql/yukon/p...30features.asp
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
This information really looks like it contains lots of
useful information. I will go over this information and
would like to set it up. Thanks and your help is really
appreciated.
-Nitin
>--Original Message--
>Nitin,
>Both SQL Server 2000 Failover Clustering and SQL Server
2000 Log Shipping are disaster recovery options. Based on
your requirements, you will need to decide what option
best suits you. It is not uncommon to
>see clients using SQL Server 2000 Failover Clustering and
SQL Server 2000 Log Shipping together also. It just
depends on their needs.
>Here is a Microsoft Knowledge Base article that explains
the various disaster recovery options
>Disaster recovery options for Microsoft SQL Server
>http://support.microsoft.com/?kbid=822400
>After reviewing this article, you may have many qs on SQL
Server 2000 Failover Clustering and SQL Server 2000 Log
Shipping. Here are some links that you may find useful
>Microsoft Whitepaper - SQL Server 2000 Failover
Clustering >>>>>>>> Has Step By Step Instructions on
installing SQL Server 2000 Failover Cluster <<<<<<<<<<
>http://www.microsoft.com/technet/pro.../sql/2000/main
tain/failclus.mspx
>Microsoft SQL Server 2000 High Availability Series
>http://www.microsoft.com/technet/pro.../sql/2000/depl
oy/sqlhalp.mspx
>If you are considering Clustering then you will need to
have a Certified Cluster solution.
>How to locate qualified cluster solutions for Windows
>http://support.microsoft.com/?id=828262
>Microsoft's Cluster support policy is explained in these
articles: Please read these carefully for the official
support policy of
>Cluster (General):
http://support.microsoft.com/default.aspx?scid=kb;en-
us;309395
>Cluster (SQL): http://support.microsoft.com/default.aspx?
scid=kb;en-us;327518
>The following links will give you more information for
Log Shipping
>INF: Frequently Asked Questions - SQL Server 2000 - Log
Shipping[vbcol=seagreen]
>http://support.microsoft.com/?kbid=314515
>Whitepaper - SQL Server 2000 How To Setup Log Shipping
Server 2000 Log Shipping <<<<<<<<<<
>http://www.microsoft.com/downloads/release.asp?
ReleaseID=30186&area=search&ordinal=31
>SQL Server 2000 Failover Clustering and Log Shipping both
are very stable and fairly simple to manage (-- that will
actually depend on the DBAs experience as these are
advanced features). Definitely,
>SQLServer 2005 will have more features as compared to SQL
Server 2000. There will be more disaster recovery options -
- for ex. Database Mirroring. For more information on SQL
Server 2005, please visit
>http://www.microsoft.com/sql/yukon/p...fo/default.asp
>Here you will find lots of whitepapers and information on
SQL Server 2005.
>HTH,
>Best Regards,
>Uttam Parui
>Microsoft Corporation
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Are you secure? For information about the Strategic
Technology Protection Program and to order your FREE
Security Tool Kit, please visit
http://www.microsoft.com/security.
>Microsoft highly recommends that users with Internet
access update their Microsoft software to better protect
against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites:
>http://www.microsoft.com/protect
>http://www.microsoft.com/security/guidance/default.mspx
>
>.
>
|||You can also check out the book SQL Server 2000 High
Availability from MS Press as well ... it goes into more
depth and has Windows Server 2003 content.
Clustering OR Shipping Log
What's the disadvantages of failover clustering over log shipping ?
Approximately how much it cost to set up the failover clustering system ?
We are planning use the log shipping to set up a standby server, but it required some down time and manual recovery, my boss asking if we can use failover clustering instead, so I have above questions in mind,
your help will be highly appreciated,
thanks a lot in advanceTo implement cluster (active-active) you have to have:
2 identical server from ms certified provider (to get support)
1 shared storage (2 servers are connected to 1 storage)
Enterprise edition of software(2X for windows and 2X for SQLserver)
Drawbacks for log shipping are:
1. You have to reconfigure clients in case of failure to hotstandby server
2. Not allways able to get latest tranactions
3. Hard to implement automatic failure detection and switching to safe host
Drawbacks for clustering:
expensive
HTH,
OBRP
Approximately how much it cost to set up the failover clustering system ?
We are planning use the log shipping to set up a standby server, but it required some down time and manual recovery, my boss asking if we can use failover clustering instead, so I have above questions in mind,
your help will be highly appreciated,
thanks a lot in advanceTo implement cluster (active-active) you have to have:
2 identical server from ms certified provider (to get support)
1 shared storage (2 servers are connected to 1 storage)
Enterprise edition of software(2X for windows and 2X for SQLserver)
Drawbacks for log shipping are:
1. You have to reconfigure clients in case of failure to hotstandby server
2. Not allways able to get latest tranactions
3. Hard to implement automatic failure detection and switching to safe host
Drawbacks for clustering:
expensive
HTH,
OBRP
Clustering or log shipping MS SQL 2000?
Our current SAP production environment consists of a window 2000 advanced
server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
server which contains an exact copy of the production database which is
up-to-date all the time during the day.
I started looking into log shipping but it appears there will be some down
time when the transaction logs are shipped from one sql server to the second
sql server. If the second sql server takes 10 minutes to apply the
transaction logs then the database is unavailable for that time period. Are
there any other options? What are other Basis admins doing? Are they using
Microsoft Clustering services to replicate the database? Or using SAN
imaging technology to replicate the data to another server?
Please advise,
Clustering won't get you there...its a high-availability solution, not
distributed processing.
The requirement of near-time data pretty much says you are looking at
transactional replication, or a 3rd party utility.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Chris,
There are several SAN Solutions that accomplish exactly what you want. This
is probably the way to go, although expensive.
-- Bill
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||replication is ideal for this. Some SAN solutions allow you to do this sort
of a thing but they tend to be very expensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Would Transactional Replication that is built into SQL 2000 work for this?
Or is this log shipping?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
> replication is ideal for this. Some SAN solutions allow you to do this
> sort of a thing but they tend to be very expensive.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Chris T." <tatroc@.donotspam.gmail.com> wrote in message
> news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
>
|||Transactional repl.
Log shipping is not going to give you the up to date you are looking for AND
the ability to use it as a reporting server. Either one, not both
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:OH%23EOy0MHHA.1252@.TK2MSFTNGP02.phx.gbl...
> Would Transactional Replication that is built into SQL 2000 work for this?
> Or is this log shipping?
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
>
server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
server which contains an exact copy of the production database which is
up-to-date all the time during the day.
I started looking into log shipping but it appears there will be some down
time when the transaction logs are shipped from one sql server to the second
sql server. If the second sql server takes 10 minutes to apply the
transaction logs then the database is unavailable for that time period. Are
there any other options? What are other Basis admins doing? Are they using
Microsoft Clustering services to replicate the database? Or using SAN
imaging technology to replicate the data to another server?
Please advise,
Clustering won't get you there...its a high-availability solution, not
distributed processing.
The requirement of near-time data pretty much says you are looking at
transactional replication, or a 3rd party utility.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Chris,
There are several SAN Solutions that accomplish exactly what you want. This
is probably the way to go, although expensive.
-- Bill
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||replication is ideal for this. Some SAN solutions allow you to do this sort
of a thing but they tend to be very expensive.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Would Transactional Replication that is built into SQL 2000 work for this?
Or is this log shipping?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
> replication is ideal for this. Some SAN solutions allow you to do this
> sort of a thing but they tend to be very expensive.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Chris T." <tatroc@.donotspam.gmail.com> wrote in message
> news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
>
|||Transactional repl.
Log shipping is not going to give you the up to date you are looking for AND
the ability to use it as a reporting server. Either one, not both
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:OH%23EOy0MHHA.1252@.TK2MSFTNGP02.phx.gbl...
> Would Transactional Replication that is built into SQL 2000 work for this?
> Or is this log shipping?
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
>
Subscribe to:
Posts (Atom)