Hello,
I have 3 registrations under a Server Group. They are all connected using
Windows NT. I was trying to use the following in SQL Query Analyzer to
execute a stored procedure that was in another registration I got the
following code from books on line:
EXEC SQL CONNECT TO "Reg2.Funds";
However, I get the error: Incorrect syntax near the keyword 'TO'.
Any help with this would be appreciated.
--
Thanks in advance,
sck10Thats for embedded SQL in C.
If you want to in SQL Server you can go by the four part name:
example:
Select * from [servername].[databasename].[owner].[objectname]
where servername can be left out if you are not using a linked server, if
you want to use a linked server (connect to any other SQL Server than the
actual one, or even another instance) you have to conigure that but adding a
new linked server.
HTH, Jens Suessmeyer.
"sck10" <sck10@.online.nospam> wrote in message
news:O9rgf2YiFHA.1480@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 3 registrations under a Server Group. They are all connected using
> Windows NT. I was trying to use the following in SQL Query Analyzer to
> execute a stored procedure that was in another registration I got the
> following code from books on line:
> EXEC SQL CONNECT TO "Reg2.Funds";
> However, I get the error: Incorrect syntax near the keyword 'TO'.
> Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>|||Hi sck10,
Thanks for your posting!
Based on my knowledge, CONNECT TO is embedded SQL for C. You cannot use it
in Query Analyzer directly. To call another SQL Server's stored procedure,
add another SQL Server as linked server and then call using the four parts
naming: [Server].[Database].[Owner].[Object]
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Monday, 19 March 2012
CONNECT TO
Hello,
I have 3 registrations under a Server Group. They are all connected using
Windows NT. I was trying to use the following in SQL Query Analyzer to
execute a stored procedure that was in another registration I got the
following code from books on line:
EXEC SQL CONNECT TO "Reg2.Funds";
However, I get the error: Incorrect syntax near the keyword 'TO'.
Any help with this would be appreciated.
Thanks in advance,
sck10
Thats for embedded SQL in C.
If you want to in SQL Server you can go by the four part name:
example:
Select * from [servername].[databasename].[owner].[objectname]
where servername can be left out if you are not using a linked server, if
you want to use a linked server (connect to any other SQL Server than the
actual one, or even another instance) you have to conigure that but adding a
new linked server.
HTH, Jens Suessmeyer.
"sck10" <sck10@.online.nospam> wrote in message
news:O9rgf2YiFHA.1480@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 3 registrations under a Server Group. They are all connected using
> Windows NT. I was trying to use the following in SQL Query Analyzer to
> execute a stored procedure that was in another registration I got the
> following code from books on line:
> EXEC SQL CONNECT TO "Reg2.Funds";
> However, I get the error: Incorrect syntax near the keyword 'TO'.
> Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
|||Hi sck10,
Thanks for your posting!
Based on my knowledge, CONNECT TO is embedded SQL for C. You cannot use it
in Query Analyzer directly. To call another SQL Server's stored procedure,
add another SQL Server as linked server and then call using the four parts
naming: [Server].[Database].[Owner].[Object]
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
I have 3 registrations under a Server Group. They are all connected using
Windows NT. I was trying to use the following in SQL Query Analyzer to
execute a stored procedure that was in another registration I got the
following code from books on line:
EXEC SQL CONNECT TO "Reg2.Funds";
However, I get the error: Incorrect syntax near the keyword 'TO'.
Any help with this would be appreciated.
Thanks in advance,
sck10
Thats for embedded SQL in C.
If you want to in SQL Server you can go by the four part name:
example:
Select * from [servername].[databasename].[owner].[objectname]
where servername can be left out if you are not using a linked server, if
you want to use a linked server (connect to any other SQL Server than the
actual one, or even another instance) you have to conigure that but adding a
new linked server.
HTH, Jens Suessmeyer.
"sck10" <sck10@.online.nospam> wrote in message
news:O9rgf2YiFHA.1480@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 3 registrations under a Server Group. They are all connected using
> Windows NT. I was trying to use the following in SQL Query Analyzer to
> execute a stored procedure that was in another registration I got the
> following code from books on line:
> EXEC SQL CONNECT TO "Reg2.Funds";
> However, I get the error: Incorrect syntax near the keyword 'TO'.
> Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
|||Hi sck10,
Thanks for your posting!
Based on my knowledge, CONNECT TO is embedded SQL for C. You cannot use it
in Query Analyzer directly. To call another SQL Server's stored procedure,
add another SQL Server as linked server and then call using the four parts
naming: [Server].[Database].[Owner].[Object]
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
CONNECT TO
Hello,
I have 3 registrations under a Server Group. They are all connected using
Windows NT. I was trying to use the following in SQL Query Analyzer to
execute a stored procedure that was in another registration I got the
following code from books on line:
EXEC SQL CONNECT TO "Reg2.Funds";
However, I get the error: Incorrect syntax near the keyword 'TO'.
Any help with this would be appreciated.
Thanks in advance,
sck10Thats for embedded SQL in C.
If you want to in SQL Server you can go by the four part name:
example:
Select * from [servername].[databasename].[owner].[objectnam
e]
where servername can be left out if you are not using a linked server, if
you want to use a linked server (connect to any other SQL Server than the
actual one, or even another instance) you have to conigure that but adding a
new linked server.
HTH, Jens Suessmeyer.
"sck10" <sck10@.online.nospam> wrote in message
news:O9rgf2YiFHA.1480@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 3 registrations under a Server Group. They are all connected using
> Windows NT. I was trying to use the following in SQL Query Analyzer to
> execute a stored procedure that was in another registration I got the
> following code from books on line:
> EXEC SQL CONNECT TO "Reg2.Funds";
> However, I get the error: Incorrect syntax near the keyword 'TO'.
> Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>|||Hi sck10,
Thanks for your posting!
Based on my knowledge, CONNECT TO is embedded SQL for C. You cannot use it
in Query Analyzer directly. To call another SQL Server's stored procedure,
add another SQL Server as linked server and then call using the four parts
naming: [Server].[Database].[Owner].[Object]
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
I have 3 registrations under a Server Group. They are all connected using
Windows NT. I was trying to use the following in SQL Query Analyzer to
execute a stored procedure that was in another registration I got the
following code from books on line:
EXEC SQL CONNECT TO "Reg2.Funds";
However, I get the error: Incorrect syntax near the keyword 'TO'.
Any help with this would be appreciated.
Thanks in advance,
sck10Thats for embedded SQL in C.
If you want to in SQL Server you can go by the four part name:
example:
Select * from [servername].[databasename].[owner].[objectnam
e]
where servername can be left out if you are not using a linked server, if
you want to use a linked server (connect to any other SQL Server than the
actual one, or even another instance) you have to conigure that but adding a
new linked server.
HTH, Jens Suessmeyer.
"sck10" <sck10@.online.nospam> wrote in message
news:O9rgf2YiFHA.1480@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 3 registrations under a Server Group. They are all connected using
> Windows NT. I was trying to use the following in SQL Query Analyzer to
> execute a stored procedure that was in another registration I got the
> following code from books on line:
> EXEC SQL CONNECT TO "Reg2.Funds";
> However, I get the error: Incorrect syntax near the keyword 'TO'.
> Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>|||Hi sck10,
Thanks for your posting!
Based on my knowledge, CONNECT TO is embedded SQL for C. You cannot use it
in Query Analyzer directly. To call another SQL Server's stored procedure,
add another SQL Server as linked server and then call using the four parts
naming: [Server].[Database].[Owner].[Object]
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, 24 February 2012
Conflict Resolution: Is defining local subscription enough: How to get log of lost record.
Hello All,
I am very much thankful to you all for providing much needed help, and
once again I am at the group with my query. In my replication
implementation in which I have around 100 subscriber I need to decide
what conflict resolution policy should be employed.
We, in our implementation just want that publisher always wins in case
if there is any conflict. Is it enough to create a local subscription
to acheieve this.
Which will ensure that in case of any conflict with the publisher
publisher always wins the conflict.
Also we want that losing party should get log of inforamtion about the
lost record, is there any way to acheive this?
Can you define what you mean by a local subscription?
The best way to alert the user of conflicts is to use the com object
C:\Program Files\Common Files\Microsoft Shared\Database
Replication\WZCNF.DLL
This will display a list of the conflicts. You will then have to poll for
them and send out alerts.
Subscriptions managed by Windows Synchronization Manager using the
interactive resolved will allow the user to manage the conflict when WSM
runs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501172243.6e17e067@.posting.google.c om...
> Hello All,
> I am very much thankful to you all for providing much needed help, and
> once again I am at the group with my query. In my replication
> implementation in which I have around 100 subscriber I need to decide
> what conflict resolution policy should be employed.
> We, in our implementation just want that publisher always wins in case
> if there is any conflict. Is it enough to create a local subscription
> to acheieve this.
> Which will ensure that in case of any conflict with the publisher
> publisher always wins the conflict.
> Also we want that losing party should get log of inforamtion about the
> lost record, is there any way to acheive this?
I am very much thankful to you all for providing much needed help, and
once again I am at the group with my query. In my replication
implementation in which I have around 100 subscriber I need to decide
what conflict resolution policy should be employed.
We, in our implementation just want that publisher always wins in case
if there is any conflict. Is it enough to create a local subscription
to acheieve this.
Which will ensure that in case of any conflict with the publisher
publisher always wins the conflict.
Also we want that losing party should get log of inforamtion about the
lost record, is there any way to acheive this?
Can you define what you mean by a local subscription?
The best way to alert the user of conflicts is to use the com object
C:\Program Files\Common Files\Microsoft Shared\Database
Replication\WZCNF.DLL
This will display a list of the conflicts. You will then have to poll for
them and send out alerts.
Subscriptions managed by Windows Synchronization Manager using the
interactive resolved will allow the user to manage the conflict when WSM
runs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501172243.6e17e067@.posting.google.c om...
> Hello All,
> I am very much thankful to you all for providing much needed help, and
> once again I am at the group with my query. In my replication
> implementation in which I have around 100 subscriber I need to decide
> what conflict resolution policy should be employed.
> We, in our implementation just want that publisher always wins in case
> if there is any conflict. Is it enough to create a local subscription
> to acheieve this.
> Which will ensure that in case of any conflict with the publisher
> publisher always wins the conflict.
> Also we want that losing party should get log of inforamtion about the
> lost record, is there any way to acheive this?
Subscribe to:
Posts (Atom)