Mirroring Client

Hello,
When a failover occurs can clients be automatically redirected to the active
instance of a db or does this have to be done with code?
Thanks in advance!
Mark,
When the database failover occurs your sessions will be disconnected. You
need to update your application to automatically fail over when this database
failover occurs.
Here is how you can do it.
Implementing Application Failover with Database Mirroring
http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/implappfailover.mspx
Hope this helps,
Ben Nevarez
"Mark" wrote:

> Hello,
> When a failover occurs can clients be automatically redirected to the active
> instance of a db or does this have to be done with code?
> Thanks in advance!
>
|||When you have a session connected to a database (principal) and the database
fails over to the mirror, your session will be disconnected. You can open a
new session and it will now be connected to the new principal (that was the
mirror before). This requires no application changes and perhaps only will
need the failover partner clause on the connection string.
But if you need application automatic failover you can implement the retry
logic described in the best practices article I mentioned here.
Hope this helps,
Ben Nevarez
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Mark,
> When the database failover occurs your sessions will be disconnected. You
> need to update your application to automatically fail over when this database
> failover occurs.
> Here is how you can do it.
> Implementing Application Failover with Database Mirroring
> http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/implappfailover.mspx
> Hope this helps,
> Ben Nevarez
>
>
> "Mark" wrote:

Mirroring Client

Hello,
When a failover occurs can clients be automatically redirected to the active
instance of a db or does this have to be done with code?
Thanks in advance!Mark,
When the database failover occurs your sessions will be disconnected. You
need to update your application to automatically fail over when this database
failover occurs.
Here is how you can do it.
Implementing Application Failover with Database Mirroring
http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/implappfailover.mspx
Hope this helps,
Ben Nevarez
"Mark" wrote:
> Hello,
> When a failover occurs can clients be automatically redirected to the active
> instance of a db or does this have to be done with code?
> Thanks in advance!
>|||When you have a session connected to a database (principal) and the database
fails over to the mirror, your session will be disconnected. You can open a
new session and it will now be connected to the new principal (that was the
mirror before). This requires no application changes and perhaps only will
need the failover partner clause on the connection string.
But if you need application automatic failover you can implement the retry
logic described in the best practices article I mentioned here.
Hope this helps,
Ben Nevarez
"Ben Nevarez" wrote:
> Mark,
> When the database failover occurs your sessions will be disconnected. You
> need to update your application to automatically fail over when this database
> failover occurs.
> Here is how you can do it.
> Implementing Application Failover with Database Mirroring
> http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/implappfailover.mspx
> Hope this helps,
> Ben Nevarez
>
>
> "Mark" wrote:
> > Hello,
> >
> > When a failover occurs can clients be automatically redirected to the active
> > instance of a db or does this have to be done with code?
> >
> > Thanks in advance!
> >

Minimum client connectivity requirement

I have Win9x clients. For them to be able to write to a
SQL database (2000), I think I would need to install
MDAC. However, many of these clients are connected with
an extremely slow WAN connection (56K) which makes MDAC
install via login script difficult or impossible. I don't
need the connectivity to all the other DB systems that
MDAC includes. Can I break it up to only install the
necessary components for TCP/IP and Named Pipes
connectivity to SQL server? If so, how can I find out
what files I need, and what if any registry entries need
to be made?
Thanks!
Installing MDAC 2.6 would be the basic requirement.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:1ce701c42706$37dc7ba0$a001280a@.phx.gbl...
> I have Win9x clients. For them to be able to write to a
> SQL database (2000), I think I would need to install
> MDAC. However, many of these clients are connected with
> an extremely slow WAN connection (56K) which makes MDAC
> install via login script difficult or impossible. I don't
> need the connectivity to all the other DB systems that
> MDAC includes. Can I break it up to only install the
> necessary components for TCP/IP and Named Pipes
> connectivity to SQL server? If so, how can I find out
> what files I need, and what if any registry entries need
> to be made?
> Thanks!
|||This is correct. There is no piecmeal approach to installing the
connectivity components to connect to SQL Server 2000.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Migrating to new domain

We are migrating to a new domain. Some clients running SQL Enterprise manag
er have been migrated to a different domain than the one the actually SQL se
rver is in. When the clients were migrated they had to reregister their ser
vers in Enterprise manager.
Where is the list of servers stored that the client had registered? Registr
y key perhaps? If so which one? I would like to retain the list that the c
lient had registered or at least be able to tell them where they can get the
list.
I can retrieve a list of servers via sqldmo but only ones that are in the ne
w domain because my machine exist in the new domain.
Any help would be appreciated.GG wrote:

> We are migrating to a new domain. Some clients running SQL
> Enterprise manager have been migrated to a different domain than the
> one the actually SQL server is in. When the clients were migrated
> they had to reregister their servers in Enterprise manager. Where is
> the list of servers stored that the client had registered? Registry
> key perhaps? If so which one? I would like to retain the list that
> the client had registered or at least be able to tell them where they
> can get the list.
> I can retrieve a list of servers via sqldmo but only ones that are in
> the new domain because my machine exist in the new domain.
The SQL Servers groups with registered servers lists are usually stored in
HKCU\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered
Servers X
But I am not sure whether you can just export/import the registry keys to
the different domain, never tried this.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank You Sabastian. That is a start. Much appreciated.