Can I combine Log Shipping and Clustering?

SQL Server 2005 SP2

Can I combine Log Shipping and Clustering? That is, can I
ship logs from the primary node in my cluster to an offsite
warm standby SQL server box?

Any help appreciated.

TIA

aj"aj" <ronald@.mcdonalds.comwrote in message
news:13k3vep1gmodlec@.news.supernews.com...

Quote:

Originally Posted by

SQL Server 2005 SP2
>
Can I combine Log Shipping and Clustering? That is, can I
ship logs from the primary node in my cluster to an offsite
warm standby SQL server box?
>

Certainly. They're two completely unrelated features.

And it's fairly common to in fact do what you propose.

Quote:

Originally Posted by

Any help appreciated.
>
TIA
>
aj

--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Can default and named instance co-exist?

I have 2 Windows 2003 servers running SQL2000. They each have separate
databases. I am in the process of clustering these 2 machines together. I
have purchased a shared external SCSI PowerVault appliance to put the quorom
and the shared databases on. I want to create a Virtual SQL server using
these 2 machines and put their separate databases on the virtual server. My
question is:
Do I have to uninstall SQL server on each machine before I install the
virtual server? If I have to I would have to restore my databases to the new
virtual server
Or can I just install a new named instance of SQL server - choosing the
virtual server in the setup? If I can do this - it would be a lot easier
moving my databases over to the new server.
If I can just create a new virtual server with leaving the original SQL in
tact - will the original still be available to my users if I decide not to
move all the databases over that day?
Is there one way that is better than the other?
1. If you want to use the exact same instance names, uninstall/reinstall for
clustering is needed. If not, you can just virtualize your new instance and
migrate data.
2. Consider reading through this kb for some details
http://support.microsoft.com/kb/224071
3. Your original instance will continue to run while you're installing a new
instance on the same node.
The bottom line, I would create a new instance and ensure it's up and
running before tinkering with the original.
-oj
"Amy Lewis" <AmyLewis@.discussions.microsoft.com> wrote in message
news:223F3934-2F36-4A2D-B5D5-D860055AE5E7@.microsoft.com...
>I have 2 Windows 2003 servers running SQL2000. They each have separate
> databases. I am in the process of clustering these 2 machines together.
> I
> have purchased a shared external SCSI PowerVault appliance to put the
> quorom
> and the shared databases on. I want to create a Virtual SQL server using
> these 2 machines and put their separate databases on the virtual server.
> My
> question is:
> Do I have to uninstall SQL server on each machine before I install the
> virtual server? If I have to I would have to restore my databases to the
> new
> virtual server
> Or can I just install a new named instance of SQL server - choosing the
> virtual server in the setup? If I can do this - it would be a lot easier
> moving my databases over to the new server.
> If I can just create a new virtual server with leaving the original SQL in
> tact - will the original still be available to my users if I decide not to
> move all the databases over that day?
> Is there one way that is better than the other?
|||Each instance of SQL Server requires its own shared disk. You can install
either 1 default instance and 15 named instances or up to 16 named
instances, but each must have its own shared drive. All drives must have a
drive letter, no mount points allowed. For existing nonclustered instances,
if you move the data files to a shared drive then you will have the option
during setup to upgrade the standalone instance to a virtual/clustered
instance (assuming you're using the Enterprise Edition setup).
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

can clustering use as load balacing

I want to have 3 MSSQL server that work at same time on shared
database(all opened a single data file on SAN for example). And request
for queries are send to those parallel and same sql servers to archive
more processing power and fail over feature?act as load balancing?
what can I do for load balancing heavy traffic queries like which can
done on web server?
thanks
SQL Server does not support shared-disk clustering for load balancing, though
there is a feature in SQL2005 called scalable shared database that allows you
to present the same database via a LUN to multiple SQL2005 instances for
read-only access.
Linchi
"Tarvirdi" wrote:

> I want to have 3 MSSQL server that work at same time on shared
> database(all opened a single data file on SAN for example). And request
> for queries are send to those parallel and same sql servers to archive
> more processing power and fail over feature?act as load balancing?
> what can I do for load balancing heavy traffic queries like which can
> done on web server?
> thanks
>
|||Linchi Shea wrote:
> SQL Server does not support shared-disk clustering for load balancing, though
> there is a feature in SQL2005 called scalable shared database that allows you
> to present the same database via a LUN to multiple SQL2005 instances for
> read-only access.
Dear Linchi,
Thanks for your response.
What you mean about sharing datafile?
For example I have A database named T1 with T1.mdf and want to have
another Database on other server(or same server to start test) and have
read only access to above T1.mdf? how implement it? which steps should I do?
I tried but failed because of "can create already exist file error"
Thanks
|||
> For example I have A database named T1 with T1.mdf and want to have
> another Database on other server(or same server to start test) and have
> read only access to above T1.mdf?
You can not do this
The limitation is NTFS, NTFS you can only have on server accessing the
volume at a time.
You can not do this on the same host either as SQL will have a problem
(cache comes to mind first)
the answer to your original question:
Q: can clustering be used as load balancing for SQL ?
A: no
|||
> there is a feature in SQL2005 called scalable shared database that allows
you
> to present the same database via a LUN to multiple SQL2005 instances for
> read-only access.
correct, but that is a "static" disk, presented RO to multiple hosts
you cannot have one host "writing" to and others "reading" from the same
disk

Can a SQL "virtual server" contains more than one SQL instance ?

Hi, I am new to SQL clustering.
I have a two nodes windows 2003 enterprise server in a cluster with sql 2000
enterprise server installed. Following the SQL installation screen I have
create a virtual server ( for SQL ) and installed the first sql instance
using "default" as the name .So far no problem.
But when I tried to install another instance of SQL it seems like I could
only create a new Virtual server and then name another SQLinstance (
example: Virtual server is " ProdSQL" and instance is INST1) , so it becomes
prodsql\inst1.
My question ( confusion ) is : can I create another instance using the same
Virtual server "prodsql" and install another instance "inst2" so this will
become prodsql\inst2. Is this possible and how to do it ?( Or one cluster
group can have only one virtual server can only have one single instance of
SQL ? )
Any advice appreciated.
George Norman
From BOL ("usually" your best buddy):
Multiple Instances of SQL Server on a Failover Cluster
You can run only one instance of SQL Server on each virtual server of a SQL
Server failover cluster, although you can install up to 16 virtual servers
on a failover cluster. The instance can be either a default instance or a
named instance. The virtual server looks like a single computer to
applications connecting to that instance of SQL Server. When applications
connect to the virtual server, they use the same convention as when
connecting to any instance of SQL Server; they specify the virtual server
name of the cluster and the optional instance name (only needed for named
instances): virtualservername\instancename. For more information about
clustering, see Failover Clustering Architecture.
joe.
"Norman" <GeorgeNorman@.hotmail.com> wrote in message
news:emEeoMuYFHA.3572@.TK2MSFTNGP12.phx.gbl...
> Hi, I am new to SQL clustering.
> I have a two nodes windows 2003 enterprise server in a cluster with sql
> 2000 enterprise server installed. Following the SQL installation screen I
> have create a virtual server ( for SQL ) and installed the first sql
> instance using "default" as the name .So far no problem.
> But when I tried to install another instance of SQL it seems like I could
> only create a new Virtual server and then name another SQLinstance (
> example: Virtual server is " ProdSQL" and instance is INST1) , so it
> becomes prodsql\inst1.
> My question ( confusion ) is : can I create another instance using the
> same Virtual server "prodsql" and install another instance "inst2" so this
> will become prodsql\inst2. Is this possible and how to do it ?( Or one
> cluster group can have only one virtual server can only have one single
> instance of SQL ? )
> Any advice appreciated.
> George Norman
>
|||Thanks Joe, that clears things up.
So when Microsoft said Multiple instance it means "multiple Virtual Servers
each with a single SQL instance" .
So does it also means that the Active -Active ( say between two nodes ) is
just running one Virtual server on each of the nodes to spread the work load
( and of course one of the node will control the quorum )?
George
"Joe Yong" <jyongNOSPAM@.scalabilityexperts.com> wrote in message
news:eJ6tUeuYFHA.3356@.TK2MSFTNGP15.phx.gbl...
> From BOL ("usually" your best buddy):
> Multiple Instances of SQL Server on a Failover Cluster
> You can run only one instance of SQL Server on each virtual server of a
> SQL Server failover cluster, although you can install up to 16 virtual
> servers on a failover cluster. The instance can be either a default
> instance or a named instance. The virtual server looks like a single
> computer to applications connecting to that instance of SQL Server. When
> applications connect to the virtual server, they use the same convention
> as when connecting to any instance of SQL Server; they specify the virtual
> server name of the cluster and the optional instance name (only needed for
> named instances): virtualservername\instancename. For more information
> about clustering, see Failover Clustering Architecture.
>
>
> joe.
> "Norman" <GeorgeNorman@.hotmail.com> wrote in message
> news:emEeoMuYFHA.3572@.TK2MSFTNGP12.phx.gbl...
>