Hello Friends
I have a project that will use Failover Cluster for SQL 2005 and NLB for the
web server front-end (using IIS).
That web application will be developed in-house. there are any special
programming considerations that the programmers must embed in the application
in order to support the special features of Failover and NLB clusters?
Does the web App Server must be Cluster-Aware to interact to SQL 2005
Failover Cluster?
Can you please give me any links to some documents that reflect these
situations?
Thanks for Help
Bruno
No. If it can connect to the SQL Server, you are set for the application.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||Any SQL client application can connect to a SQL Cluster with no changes. I
recommend using non-persistent connections so the web app can recover in
case of a cluster failover, but that has been general programming practice
for a while now. Your NLB session model and the application session model
will need to work together. I.E. if you only support local sessions in IIS,
you will need to make sure your NLB sessions are "sticky". Your Network
Engineer can help with this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||You need to have reconnect logic built into the application. Whenever a
failover occurs, you will loose connectivity. The advantage of this
solution, however, is that the failover happens automatically, and is
relatively brief.
On the NLB, you need to program "stateless" apps. That is, you can not
guarantee that recovered session are redirect to the same web server during
each pass. If only one server is aware of the state, you find the user
orphaned if redirected to one of the other servers.
Also, to keep your solution clean and to harden security, consider using
some sort of middleware, either through dedicated application hosts, or some
sort of messaging platform.
Sincerely,
Anthony Thomas
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
Showing posts with label nlb. Show all posts
Showing posts with label nlb. Show all posts
Tuesday, March 20, 2012
NLB drainstop command issues
Hello,
We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.
The applications make DB connections using standard .NET System.Data classes.
Has anyone experienced this before? Any pointers on what to check for?
Thanks
Alexwhich database is this?
you have posted in the non-database-specific "database concepts" forum, and it sounds like this thread should be moved to a database-specific forum|||Thanks. I'll post it in the sql server forum.|||Hello,
We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.
The applications make DB connections using standard .NET System.Data classes.
The database servers are SQL Server 2005.
Has anyone experienced this before? Any pointers on what to check for?
Thanks
Alex|||no, don't do that, we'll just move this thread over there
:)|||no, don't do that, we'll just move this thread over there
:)Hehe!! :) Thank you sir!
I hope someone here can assist!
We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.
The applications make DB connections using standard .NET System.Data classes.
Has anyone experienced this before? Any pointers on what to check for?
Thanks
Alexwhich database is this?
you have posted in the non-database-specific "database concepts" forum, and it sounds like this thread should be moved to a database-specific forum|||Thanks. I'll post it in the sql server forum.|||Hello,
We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.
The applications make DB connections using standard .NET System.Data classes.
The database servers are SQL Server 2005.
Has anyone experienced this before? Any pointers on what to check for?
Thanks
Alex|||no, don't do that, we'll just move this thread over there
:)|||no, don't do that, we'll just move this thread over there
:)Hehe!! :) Thank you sir!
I hope someone here can assist!
NLB and SQL2005
Hi,
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
CraigThere is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a
mirrored database and
use that snapshot as a read-only database. However, you will work against a
snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only d
ata using the SSB
thinking: http://support.microsoft.com/?kbid=910378
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balanc
ing support.
> Now that it's (more or less) out, the documentation makes no mention of su
pport for NLB.
> There's talk of clusters, mirroring and replication and while mirroring se
ems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have though
t it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
CraigThere is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a
mirrored database and
use that snapshot as a read-only database. However, you will work against a
snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only d
ata using the SSB
thinking: http://support.microsoft.com/?kbid=910378
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balanc
ing support.
> Now that it's (more or less) out, the documentation makes no mention of su
pport for NLB.
> There's talk of clusters, mirroring and replication and while mirroring se
ems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have though
t it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
NLB and SQL2005
Hi,
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
CraigThere is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
--
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a mirrored database and
use that snapshot as a read-only database. However, you will work against a snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only data using the SSB
thinking: http://support.microsoft.com/?kbid=910378
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring seems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have thought it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
CraigThere is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
--
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a mirrored database and
use that snapshot as a read-only database. However, you will work against a snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only data using the SSB
thinking: http://support.microsoft.com/?kbid=910378
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring seems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have thought it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
NLB and SQL2005
Hi,
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
Craig
There is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a mirrored database and
use that snapshot as a read-only database. However, you will work against a snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only data using the SSB
thinking: http://support.microsoft.com/?kbid=910378
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring seems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have thought it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
early on in SQL2005 (Yukon's) life, there was talk for Network Load
Balancing support.
Now that it's (more or less) out, the documentation makes no mention of
support for NLB.
There's talk of clusters, mirroring and replication and while mirroring
seems to come close, it's still and active/passive configuration (with the
addition of a watcher!).
Hopefully this is just buried in the docs somewhere on the install CD (I'm
waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
but I'd have thought it would be online somewhere.
Anyone spotted it?
Thanks
Craig
There is no "NLB" or other form of transparent SQL scale-out in SQL Server
2005 (other than the Distributed Partitioned Views carried over from SQL
Server 2000). Mirroring does allow the mirror copy to be accessed read-only
for reporting. And there is a shared read-only reporting database feature.
In some cases those address the need for scale-out.
There is the notion of a Service-Oriented Database Architecture (SODA) in
SQL Server 2005 that can be used to achieve scale-out. It is transparent at
the level of a service interface, not at the level of SQL. It isn't
explicitly talked about in BOL. I wrote a white paper about it a year ago,
but haven't seen Microsoft publish it yet. It was supposed to be available
at launch. Dave Campbell has given presentations on it, at launch and I
believe also at PDC (and perhaps PASS).
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load
> Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of
> support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring
> seems to come close, it's still and active/passive configuration (with the
> addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm
> waiting for the Dec MSDN DVDs, which presumably will include SQL2005 RTM),
> but I'd have thought it would be online somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
|||In addition to Hal's comments:
For mirroring, you will probably be able to define a database snapshot of a mirrored database and
use that snapshot as a read-only database. However, you will work against a snapshot which will be
up to as old as the interval for creating the snapshots.
Also, you can have several database instances accessing the same read-only data using the SSB
thinking: http://support.microsoft.com/?kbid=910378
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Craig Humphrey" <CraigHumphreyHatesSpam@.newsgroup.nospam> wrote in message
news:uWpmgmX6FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> early on in SQL2005 (Yukon's) life, there was talk for Network Load Balancing support.
> Now that it's (more or less) out, the documentation makes no mention of support for NLB.
> There's talk of clusters, mirroring and replication and while mirroring seems to come close, it's
> still and active/passive configuration (with the addition of a watcher!).
> Hopefully this is just buried in the docs somewhere on the install CD (I'm waiting for the Dec
> MSDN DVDs, which presumably will include SQL2005 RTM), but I'd have thought it would be online
> somewhere.
> Anyone spotted it?
> Thanks
> Craig
>
Subscribe to:
Posts (Atom)