Mirrored linked server failover.

We have a mirrored db setup, with a third server that needs to be linked to this mirrored setup as a linked server. The link server setup only allows you to specify the primary server. How will the linked server setup know what the secondary server is? Thanks

It's not clear which way you are creating the linked server:

If it is from the primary->third server then you will need to create the linked server on both the principal and mirror since it does not automatically failover (it's defined at the instance level and not the database level).

If it is from the third server->primary then ensure you set the failover partner property in the linked server and that the default database is specified (catalog in provider speak). For example

EXEC master.dbo.sp_addlinkedserver

@.server = N'matthol11',

@.srvproduct=N'',

@.provider=N'SQLNCLI',

@.catalog=N'test',

@.provstr=N'Server=matthol11;FailoverPartner=matthol6;'

select*from matthol11.test.dbo.test

Regards,

Matt

Mirrored linked server failover.

We have a mirror setup, with a third server that needs to be linked to this mirrored setup. The link server setup only allows you to specify the primary server. How will the linked server setup know what the secondary server is? Thanks

Andre,

You can specify the partner name in the linked server server properties and the linked server will automatically failover from the principal to the mirror if the principal is failed over.

Regards,

Matt Hollingswort

Sr. Program Manager

Microsoft SQL Server

sql

Mirrored linked server failover.

We have a mirrored db setup, with a third server that needs to be linked to this mirrored setup as a linked server. The link server setup only allows you to specify the primary server. How will the linked server setup know what the secondary server is? Thanks

It's not clear which way you are creating the linked server:

If it is from the primary->third server then you will need to create the linked server on both the principal and mirror since it does not automatically failover (it's defined at the instance level and not the database level).

If it is from the third server->primary then ensure you set the failover partner property in the linked server and that the default database is specified (catalog in provider speak). For example

EXEC master.dbo.sp_addlinkedserver

@.server = N'matthol11',

@.srvproduct=N'',

@.provider=N'SQLNCLI',

@.catalog=N'test',

@.provstr=N'Server=matthol11;FailoverPartner=matthol6;'

select * from matthol11.test.dbo.test

Regards,

Matt

Mirrored linked server failover.

We have a mirror setup, with a third server that needs to be linked to this mirrored setup. The link server setup only allows you to specify the primary server. How will the linked server setup know what the secondary server is? Thanks

Andre,

You can specify the partner name in the linked server server properties and the linked server will automatically failover from the principal to the mirror if the principal is failed over.

Regards,

Matt Hollingswort

Sr. Program Manager

Microsoft SQL Server

Migration to sql server on network for access database

hi,

I migrated the Northwind database using SQL Migration Assistant for Access. it worked fine and I was able to link the access forms to Local machine SQL Server 2005 and it worked fine.

Now i want to link the same Northwind access database to Another Server on the network.

When i try to run the wizard again, it won't migrate the user objects like tables to server, it will just create a database and that is it.

it will give me this error too.

No User objects were selected.

any idea,

Thanks,

---

Fahim

Since you have already migrated to your local SQL Server, you could use the Import/Export Wizard to move the tables to a different SQL Server.

In the Object Explorer, right-click on the database, select [Task..], and then click on Export Data...

Migration from DTS to SSIS

Hi everybody,

I would REALLY appreciate it if some had a link to a good tutorial about migration from DTS to SSIS, but without visual studio . net.

For example I need to use DTS package in sql server 2005 and execute them, I used migration wizard (SQL 2005) but it didn't work because i have in my computer sql 2000 et sql 2005 and the server name is PC2, however when i use the server source PC2 and the server destination PC2 an error message appear "server destination should be a sql server 2005 instance ".

help me please..

Thanks very much anyone response my question.

Moving to the SSIS 2005 forum from the SSIS 2008 forum.|||

If the connection is to a computer with both 2000 and 2005 on it, the 2005 install needs to be referenced by the server and instance name (MACHINENAME\INSTANCENAME).

Migration from DTS to SSIS

Hi everybody,

I would REALLY appreciate it if some had a link to a good tutorial about migration from DTS to SSIS, but without visual studio . net.

For example I need to use DTS package in sql server 2005 and execute them, I used migration wizard (SQL 2005) but it didn't work because i have in my computer sql 2000 et sql 2005 and the server name is PC2, however when i use the server source PC2 and the server destination PC2 an error message appear "server destination should be a sql server 2005 instance ".

help me please..

Thanks very much anyone response my question.

Moving to the SSIS 2005 forum from the SSIS 2008 forum.|||

If the connection is to a computer with both 2000 and 2005 on it, the 2005 install needs to be referenced by the server and instance name (MACHINENAME\INSTANCENAME).

Migration ACCESS --> SQL Linked table

Hi again,
I have paradox table linked in an access database. I want to migrate to SQL.
Can I link these tables in SQL ?
ThanksAccess does a better job of linking to ISAMs than SQLS does (which
uses the Jet provider). Is there any way you can migrate ALL of the
data? If linking to other ISAMs is a big part of your app, you might
be better keeping that part of it in Access/Jet. You can always link
to SQL Server tables as well.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Thu, 6 Nov 2003 17:23:19 -0500, "Sylvain Provencher"
<sylvain.provencher@.nobelia.com> wrote:
>Hi again,
>I have paradox table linked in an access database. I want to migrate to SQL.
>Can I link these tables in SQL ?
>Thanks
>