Does SQL Server 2005 Express support Web/Internet Replication to other SQL Server Express Client

HI

Q1: Does Sql Server 2005 Express support Web/Internet to other SQL Server 2005 Express Clients or does it have to Synch across the internet to a fully installed setup SQL Server 2005 with IIS?

Q2: Does SQL Server 2005 Express support Direct Replication between other SQL Server 2005 Express clients?

Regards

Shabby wrote:

HI

Q1: Does Sql Server 2005 Express support Web/Internet to other SQL Server 2005 Express Clients or does it have to Synch across the internet to a fully installed setup SQL Server 2005 with IIS?

You have to sync to a SS2005 with IIS. Replication doesn't support sync between sql express.

Shabby wrote:

Q2: Does SQL Server 2005 Express support Direct Replication between other SQL Server 2005 Express clients?

Regards

No Sql 2005 express cannot sync with sql 2005 express directly.

|||

SQL Server 2005 Express Edition supports being a replication subscriber only. See http://msdn2.microsoft.com/en-us/library/ms165700.aspx The publisher and distributor must be higher SKUs of SQL Server 2005. i.e. Enterprise, Standard, Workgroup. As for synching via IIS over the internet with merge replication, this is supported by the SQL Server 2005 Express client.

Hope this helps,

Tom

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Express edition can only be used as a subscriber, including direct SQL replication or web sync. Please take a look at this link for replication features supported by various editions (http://msdn2.microsoft.com/en-us/library/ms143761.aspx).

Thanks,

Peng

|||

Peng Song wrote:

Express edition can only be used as a subscriber, including direct SQL replication or web sync. Please take a look at this link for replication features supported by various editions (http://msdn2.microsoft.com/en-us/library/ms143761.aspx).

Thanks,

Peng

does the client (subscriber) running on sql server express has to have IIS or only the publishing pc? thanks

sql

Does SQL Server 2005 Express support Web/Internet Replication to other SQL Server Express Cl

HI

Q1: Does Sql Server 2005 Express support Web/Internet to other SQL Server 2005 Express Clients or does it have to Synch across the internet to a fully installed setup SQL Server 2005 with IIS?

Q2: Does SQL Server 2005 Express support Direct Replication between other SQL Server 2005 Express clients?

Regards

Shabby wrote:

HI

Q1: Does Sql Server 2005 Express support Web/Internet to other SQL Server 2005 Express Clients or does it have to Synch across the internet to a fully installed setup SQL Server 2005 with IIS?

You have to sync to a SS2005 with IIS. Replication doesn't support sync between sql express.

Shabby wrote:

Q2: Does SQL Server 2005 Express support Direct Replication between other SQL Server 2005 Express clients?

Regards

No Sql 2005 express cannot sync with sql 2005 express directly.

|||

SQL Server 2005 Express Edition supports being a replication subscriber only. See http://msdn2.microsoft.com/en-us/library/ms165700.aspx The publisher and distributor must be higher SKUs of SQL Server 2005. i.e. Enterprise, Standard, Workgroup. As for synching via IIS over the internet with merge replication, this is supported by the SQL Server 2005 Express client.

Hope this helps,

Tom

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Express edition can only be used as a subscriber, including direct SQL replication or web sync. Please take a look at this link for replication features supported by various editions (http://msdn2.microsoft.com/en-us/library/ms143761.aspx).

Thanks,

Peng

|||

Peng Song wrote:

Express edition can only be used as a subscriber, including direct SQL replication or web sync. Please take a look at this link for replication features supported by various editions (http://msdn2.microsoft.com/en-us/library/ms143761.aspx).

Thanks,

Peng

does the client (subscriber) running on sql server express has to have IIS or only the publishing pc? thanks

Does not have permission to register endpoint

I came across with the problem that I cannot create an endpoint on Windows Server 2003 (SP1). It's said:

Msg 7850, Level 16, State 1, Line 2

The user 'yyyyy\xxxx' does not have permission to register endpoint 'zzzzzz' on the specified URL. Please ensure the URL refers to a namespace that is reserved for listening by SQL.

Msg 7807, Level 16, State 1, Line 2

An error ('0x80070005') occurred while attempting to register the endpoint 'SecurityServices'.

My code looks loke this:

IF EXISTS (

SELECT name from sys.http_endpoints

WHERE name = 'zzzzzz'

)

DROP ENDPOINT zzzzzz

GO

CREATE ENDPOINT zzzzzz

STATE = STARTED

AS HTTP (

path='/sql/zzzzzz',

AUTHENTICATION=(INTEGRATED),

PORTS = (CLEAR)

)

FOR SOAP(

WEBMETHOD 'http://servername/' . 'sp1' (NAME = 'dbName.dbo.sp1'),

WEBMETHOD 'http://servername/' . 'sp2' (NAME = 'dbName.dbo.sp2'),

WSDL = DEFAULT,

BATCHES=ENABLED)

GO

-- End of Script --
The script that I use is correct and it works fine on my local machine (Windows XP). The user that I used to crete an endpoint on the server has 'sysadmin' level. The IIS was already turned off. Also I run the script by using the RemoteDesktop to connect to the server (Windows 2003) that has SQL Server 2005.

If anyone has an idea about my problem, please help me !!!

Thank you,
POP

I believe the problem you run into is because when you create an endpoint, you are not executing under the logged in user, but as the account the SQL Server runs under. In your case the account on the remote server most likely have very restricted priviliges. To fix this you need to reserve the namespace you are going to create, before you can actually create it.
To reserve it, you run the un-doc:ed stored procedure sp_reserve_http_namespace. You run it with the macine name (as it will appear in the site param in CREATE ENDPOINT), portnumber and virtual directory name as in the path param in CREATE ENDPOINT.
An example would be:
sp_reserve_http_namespace N'http://Perth:80/emp', which then would have the following CREATE ENPOINT statement:
<<<<<<<<<<<<<<<
create endpoint EmpClass
state = started
as HTTP (
site = 'Perth',
path = '/emp',
authentication = (INTEGRATED),
ports = (CLEAR))
FOR SOAP...
>>>>>>>>>>>>>>>
Hope this helps!!
Niels

|||Thank you so much Niels (again),

It's works !!!!

At first, I try to use >> sp_reserve_http_namespace N'http://Perth:80/emp'
first but it said >> A reservation for this HTTP namespace (http://Perth:80/emp) already exists

But when I look at your code
as HTTP (
site = 'Perth',
path = '/emp',
authentication = (INTEGRATED),
ports = (CLEAR))
FOR SOAP...
I don't have the value of the site (yellow highlighted part). Then I add that part and when I run the code on the server, it works !!!!.

Without that line, I can create an end point on my local computer but not on the server (Cluster Servers). So from now on, I'll have that line all the time.

Thank you again Niels,

POP|||It works. Thank you.

Does not have permission to register endpoint

I came across with the problem that I cannot create an endpoint on Windows Server 2003 (SP1). It's said:

Msg 7850, Level 16, State 1, Line 2

The user 'yyyyy\xxxx' does not have permission to register endpoint 'zzzzzz' on the specified URL. Please ensure the URL refers to a namespace that is reserved for listening by SQL.

Msg 7807, Level 16, State 1, Line 2

An error ('0x80070005') occurred while attempting to register the endpoint 'SecurityServices'.

My code looks loke this:

IF EXISTS (

SELECT name from sys.http_endpoints

WHERE name = 'zzzzzz'

)

DROP ENDPOINT zzzzzz

GO

CREATE ENDPOINT zzzzzz

STATE = STARTED

AS HTTP (

path='/sql/zzzzzz',

AUTHENTICATION=(INTEGRATED),

PORTS = (CLEAR)

)

FOR SOAP(

WEBMETHOD 'http://servername/' . 'sp1' (NAME = 'dbName.dbo.sp1'),

WEBMETHOD 'http://servername/' . 'sp2' (NAME = 'dbName.dbo.sp2'),

WSDL = DEFAULT,

BATCHES=ENABLED)

GO

-- End of Script --
The script that I use is correct and it works fine on my local machine (Windows XP). The user that I used to crete an endpoint on the server has 'sysadmin' level. The IIS was already turned off. Also I run the script by using the RemoteDesktop to connect to the server (Windows 2003) that has SQL Server 2005.

If anyone has an idea about my problem, please help me !!!

Thank you,
POP

I believe the problem you run into is because when you create an endpoint, you are not executing under the logged in user, but as the account the SQL Server runs under. In your case the account on the remote server most likely have very restricted priviliges. To fix this you need to reserve the namespace you are going to create, before you can actually create it.
To reserve it, you run the un-doc:ed stored procedure sp_reserve_http_namespace. You run it with the macine name (as it will appear in the site param in CREATE ENDPOINT), portnumber and virtual directory name as in the path param in CREATE ENDPOINT.
An example would be:
sp_reserve_http_namespace N'http://Perth:80/emp', which then would have the following CREATE ENPOINT statement:
<<<<<<<<<<<<<<<
create endpoint EmpClass
state = started
as HTTP (
site = 'Perth',
path = '/emp',
authentication = (INTEGRATED),
ports = (CLEAR))
FOR SOAP...
>>>>>>>>>>>>>>>
Hope this helps!!
Niels
|||Thank you so much Niels (again),

It's works !!!!

At first, I try to use >> sp_reserve_http_namespace N'http://Perth:80/emp'
first but it said >> A reservation for this HTTP namespace (http://Perth:80/emp) already exists

But when I look at your code
as HTTP (
site = 'Perth',
path = '/emp',
authentication = (INTEGRATED),
ports = (CLEAR))
FOR SOAP...
I don't have the value of the site (yellow highlighted part). Then I add that part and when I run the code on the server, it works !!!!.

Without that line, I can create an end point on my local computer but not on the server (Cluster Servers). So from now on, I'll have that line all the time.

Thank you again Niels,

POP|||It works. Thank you.