Publish Sql on the internet

Hi,
I need to publish my computer on the internet which is on a company network.
in the network we have a server that connects to the internet and gives
internet access to all the company computers.
I'm running a sql server on my compuer and I need to access it through the
internet.
Also, I need to know how do I secure the connection to my
server/computer/company.
Any info on this would be great!!
Tomer,
I had a bit of trouble understanding what you are asking, I will recap.
You have a corporate network connected to the internet via a proxy
server (let's call this PROXY1). You want to "publish" your computer on
the internet, which resides behind PROXY1. What do you mean by
"publish"? Is it a web site, an FTP site, a database, remote desktop
connection, what?
You are running SQL Server on "my computer". Is this in the corporate
network or on the internet at home? Please clarify these points very
carefully (take a bit of time) as they will have a significant bearing
on the accuracy of the responses you will get.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> I need to publish my computer on the internet which is on a company network.
> in the network we have a server that connects to the internet and gives
> internet access to all the company computers.
> I'm running a sql server on my compuer and I need to access it through the
> internet.
> Also, I need to know how do I secure the connection to my
> server/computer/company.
> Any info on this would be great!!
>
|||Hi,
My computer is part of the company computer network and connects to the
internet through the company server which connects to the internet with an
adsl modem installed on it.
I have a sql server 2000 installed on my computer and I wish to access it
from 'outside' through the internet and access its databases.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Tomer,
> I had a bit of trouble understanding what you are asking, I will recap.
> You have a corporate network connected to the internet via a proxy
> server (let's call this PROXY1). You want to "publish" your computer on
> the internet, which resides behind PROXY1. What do you mean by
> "publish"? Is it a web site, an FTP site, a database, remote desktop
> connection, what?
> You are running SQL Server on "my computer". Is this in the corporate
> network or on the internet at home? Please clarify these points very
> carefully (take a bit of time) as they will have a significant bearing
> on the accuracy of the responses you will get.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
network.[vbcol=seagreen]
the[vbcol=seagreen]
|||Tomer,
You will need to use NAT to allow your computer to act as a server. I
would only do this sort of thing at home and never on a corporate network.
On a corporate network you should have a demilitarised zone (DMZ) that
allows incoming connections from the internet. I really do not recommend
allow people from the public internet to connect directly to your LAN,
you are asking for trouble. The DMZ should not be able to initiate
connections to your LAN.
I would go further and not even allow any form of direct access to a
database server from the internet. Use a web server in a DMZ to connect
to your db server (also in a separate DMZ) to serve information. If you
need to manage a SQL Server from the internet you could use the web
administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
(http://www.mylittletools.net).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> My computer is part of the company computer network and connects to the
> internet through the company server which connects to the internet with an
> adsl modem installed on it.
> I have a sql server 2000 installed on my computer and I wish to access it
> from 'outside' through the internet and access its databases.
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...
>
> network.
>
> the
>
>
|||Hi,
First thing, thanks alot for the info! I know that this is a problematic
issue in security, but I need to connect a pocket pc device with a gprs
modem directly to the sql server, and I'd rather not use a web service
application.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OOIKLZsfEHA.1424@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Tomer,
> You will need to use NAT to allow your computer to act as a server. I
> would only do this sort of thing at home and never on a corporate network.
> On a corporate network you should have a demilitarised zone (DMZ) that
> allows incoming connections from the internet. I really do not recommend
> allow people from the public internet to connect directly to your LAN,
> you are asking for trouble. The DMZ should not be able to initiate
> connections to your LAN.
> I would go further and not even allow any form of direct access to a
> database server from the internet. Use a web server in a DMZ to connect
> to your db server (also in a separate DMZ) to serve information. If you
> need to manage a SQL Server from the internet you could use the web
> administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
> (http://www.mylittletools.net).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
an[vbcol=seagreen]
it[vbcol=seagreen]
|||OK,
What you need to do is NOT allow connections into your LAN. Create a DMZ
and place the SQL Server there. Do not allow the DMZ to initiate
connections into the LAN. Only allow connections from the LAN TO the DMZ.
Do not allow SQL Server to connect to anything else on your network.
Remember, if this machine is compromised, you could be in trouble. On
the firewall, only open one port to the SQL Server, and make sure this
is not 1433. Make it a high port number such as 56378 (or whatever).
Ensure SQL Server is listening on this port.
This will put you out of range of port scanners that are only looking
for common ports such as 139, 1433, etc, however will not protect you
from someone scanning every port on your machine, but then there are
intrusion detection tools available to protect you from this.
Another way to do this is to use a VPN tunnel from the client on the
internet, through a VPN server in a DMZ on your corporate network, and
then you can use the entire LAN. This might be easier to set up and
configure, then again it might not.
Whatever you do, do not allow direct connections from the public
internet, unencrypted into your LAN.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> First thing, thanks alot for the info! I know that this is a problematic
> issue in security, but I need to connect a pocket pc device with a gprs
> modem directly to the sql server, and I'd rather not use a web service
> application.
>
|||Thanks a bunch!! this helps alot
Tomer.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u$IWGX4fEHA.632@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> OK,
> What you need to do is NOT allow connections into your LAN. Create a DMZ
> and place the SQL Server there. Do not allow the DMZ to initiate
> connections into the LAN. Only allow connections from the LAN TO the DMZ.
> Do not allow SQL Server to connect to anything else on your network.
> Remember, if this machine is compromised, you could be in trouble. On
> the firewall, only open one port to the SQL Server, and make sure this
> is not 1433. Make it a high port number such as 56378 (or whatever).
> Ensure SQL Server is listening on this port.
> This will put you out of range of port scanners that are only looking
> for common ports such as 139, 1433, etc, however will not protect you
> from someone scanning every port on your machine, but then there are
> intrusion detection tools available to protect you from this.
> Another way to do this is to use a VPN tunnel from the client on the
> internet, through a VPN server in a DMZ on your corporate network, and
> then you can use the entire LAN. This might be easier to set up and
> configure, then again it might not.
> Whatever you do, do not allow direct connections from the public
> internet, unencrypted into your LAN.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:

Publish Sql on the internet

Hi,
I need to publish my computer on the internet which is on a company network.
in the network we have a server that connects to the internet and gives
internet access to all the company computers.
I'm running a sql server on my compuer and I need to access it through the
internet.
Also, I need to know how do I secure the connection to my
server/computer/company.
Any info on this would be great!!Tomer,
I had a bit of trouble understanding what you are asking, I will recap.
You have a corporate network connected to the internet via a proxy
server (let's call this PROXY1). You want to "publish" your computer on
the internet, which resides behind PROXY1. What do you mean by
"publish"? Is it a web site, an FTP site, a database, remote desktop
connection, what?
You are running SQL Server on "my computer". Is this in the corporate
network or on the internet at home? Please clarify these points very
carefully (take a bit of time) as they will have a significant bearing
on the accuracy of the responses you will get.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> I need to publish my computer on the internet which is on a company networ
k.
> in the network we have a server that connects to the internet and gives
> internet access to all the company computers.
> I'm running a sql server on my compuer and I need to access it through the
> internet.
> Also, I need to know how do I secure the connection to my
> server/computer/company.
> Any info on this would be great!!
>|||Hi,
My computer is part of the company computer network and connects to the
internet through the company server which connects to the internet with an
adsl modem installed on it.
I have a sql server 2000 installed on my computer and I wish to access it
from 'outside' through the internet and access its databases.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Tomer,
> I had a bit of trouble understanding what you are asking, I will recap.
> You have a corporate network connected to the internet via a proxy
> server (let's call this PROXY1). You want to "publish" your computer on
> the internet, which resides behind PROXY1. What do you mean by
> "publish"? Is it a web site, an FTP site, a database, remote desktop
> connection, what?
> You are running SQL Server on "my computer". Is this in the corporate
> network or on the internet at home? Please clarify these points very
> carefully (take a bit of time) as they will have a significant bearing
> on the accuracy of the responses you will get.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
network.[vbcol=seagreen]
the[vbcol=seagreen]|||Tomer,
You will need to use NAT to allow your computer to act as a server. I
would only do this sort of thing at home and never on a corporate network.
On a corporate network you should have a demilitarised zone (DMZ) that
allows incoming connections from the internet. I really do not recommend
allow people from the public internet to connect directly to your LAN,
you are asking for trouble. The DMZ should not be able to initiate
connections to your LAN.
I would go further and not even allow any form of direct access to a
database server from the internet. Use a web server in a DMZ to connect
to your db server (also in a separate DMZ) to serve information. If you
need to manage a SQL Server from the internet you could use the web
administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
(http://www.mylittletools.net).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> My computer is part of the company computer network and connects to the
> internet through the company server which connects to the internet with an
> adsl modem installed on it.
> I have a sql server 2000 installed on my computer and I wish to access it
> from 'outside' through the internet and access its databases.
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...
>
> network.
>
> the
>
>
>|||Hi,
First thing, thanks alot for the info! I know that this is a problematic
issue in security, but I need to connect a pocket pc device with a gprs
modem directly to the sql server, and I'd rather not use a web service
application.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OOIKLZsfEHA.1424@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Tomer,
> You will need to use NAT to allow your computer to act as a server. I
> would only do this sort of thing at home and never on a corporate network.
> On a corporate network you should have a demilitarised zone (DMZ) that
> allows incoming connections from the internet. I really do not recommend
> allow people from the public internet to connect directly to your LAN,
> you are asking for trouble. The DMZ should not be able to initiate
> connections to your LAN.
> I would go further and not even allow any form of direct access to a
> database server from the internet. Use a web server in a DMZ to connect
> to your db server (also in a separate DMZ) to serve information. If you
> need to manage a SQL Server from the internet you could use the web
> administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
> (http://www.mylittletools.net).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
an[vbcol=seagreen]
it[vbcol=seagreen]|||OK,
What you need to do is NOT allow connections into your LAN. Create a DMZ
and place the SQL Server there. Do not allow the DMZ to initiate
connections into the LAN. Only allow connections from the LAN TO the DMZ.
Do not allow SQL Server to connect to anything else on your network.
Remember, if this machine is compromised, you could be in trouble. On
the firewall, only open one port to the SQL Server, and make sure this
is not 1433. Make it a high port number such as 56378 (or whatever).
Ensure SQL Server is listening on this port.
This will put you out of range of port scanners that are only looking
for common ports such as 139, 1433, etc, however will not protect you
from someone scanning every port on your machine, but then there are
intrusion detection tools available to protect you from this.
Another way to do this is to use a VPN tunnel from the client on the
internet, through a VPN server in a DMZ on your corporate network, and
then you can use the entire LAN. This might be easier to set up and
configure, then again it might not.
Whatever you do, do not allow direct connections from the public
internet, unencrypted into your LAN.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> First thing, thanks alot for the info! I know that this is a problematic
> issue in security, but I need to connect a pocket pc device with a gprs
> modem directly to the sql server, and I'd rather not use a web service
> application.
>|||Thanks a bunch!! this helps alot
Tomer.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u$IWGX4fEHA.632@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> OK,
> What you need to do is NOT allow connections into your LAN. Create a DMZ
> and place the SQL Server there. Do not allow the DMZ to initiate
> connections into the LAN. Only allow connections from the LAN TO the DMZ.
> Do not allow SQL Server to connect to anything else on your network.
> Remember, if this machine is compromised, you could be in trouble. On
> the firewall, only open one port to the SQL Server, and make sure this
> is not 1433. Make it a high port number such as 56378 (or whatever).
> Ensure SQL Server is listening on this port.
> This will put you out of range of port scanners that are only looking
> for common ports such as 139, 1433, etc, however will not protect you
> from someone scanning every port on your machine, but then there are
> intrusion detection tools available to protect you from this.
> Another way to do this is to use a VPN tunnel from the client on the
> internet, through a VPN server in a DMZ on your corporate network, and
> then you can use the entire LAN. This might be easier to set up and
> configure, then again it might not.
> Whatever you do, do not allow direct connections from the public
> internet, unencrypted into your LAN.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:

Publish Sql on the internet

Hi,
I need to publish my computer on the internet which is on a company network.
in the network we have a server that connects to the internet and gives
internet access to all the company computers.
I'm running a sql server on my compuer and I need to access it through the
internet.
Also, I need to know how do I secure the connection to my
server/computer/company.
Any info on this would be great!!Tomer,
I had a bit of trouble understanding what you are asking, I will recap.
You have a corporate network connected to the internet via a proxy
server (let's call this PROXY1). You want to "publish" your computer on
the internet, which resides behind PROXY1. What do you mean by
"publish"? Is it a web site, an FTP site, a database, remote desktop
connection, what?
You are running SQL Server on "my computer". Is this in the corporate
network or on the internet at home? Please clarify these points very
carefully (take a bit of time) as they will have a significant bearing
on the accuracy of the responses you will get.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> I need to publish my computer on the internet which is on a company network.
> in the network we have a server that connects to the internet and gives
> internet access to all the company computers.
> I'm running a sql server on my compuer and I need to access it through the
> internet.
> Also, I need to know how do I secure the connection to my
> server/computer/company.
> Any info on this would be great!!
>|||Hi,
My computer is part of the company computer network and connects to the
internet through the company server which connects to the internet with an
adsl modem installed on it.
I have a sql server 2000 installed on my computer and I wish to access it
from 'outside' through the internet and access its databases.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...
> Tomer,
> I had a bit of trouble understanding what you are asking, I will recap.
> You have a corporate network connected to the internet via a proxy
> server (let's call this PROXY1). You want to "publish" your computer on
> the internet, which resides behind PROXY1. What do you mean by
> "publish"? Is it a web site, an FTP site, a database, remote desktop
> connection, what?
> You are running SQL Server on "my computer". Is this in the corporate
> network or on the internet at home? Please clarify these points very
> carefully (take a bit of time) as they will have a significant bearing
> on the accuracy of the responses you will get.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
> > Hi,
> > I need to publish my computer on the internet which is on a company
network.
> > in the network we have a server that connects to the internet and gives
> > internet access to all the company computers.
> > I'm running a sql server on my compuer and I need to access it through
the
> > internet.
> > Also, I need to know how do I secure the connection to my
> > server/computer/company.
> >
> > Any info on this would be great!!
> >
> >|||Tomer,
You will need to use NAT to allow your computer to act as a server. I
would only do this sort of thing at home and never on a corporate network.
On a corporate network you should have a demilitarised zone (DMZ) that
allows incoming connections from the internet. I really do not recommend
allow people from the public internet to connect directly to your LAN,
you are asking for trouble. The DMZ should not be able to initiate
connections to your LAN.
I would go further and not even allow any form of direct access to a
database server from the internet. Use a web server in a DMZ to connect
to your db server (also in a separate DMZ) to serve information. If you
need to manage a SQL Server from the internet you could use the web
administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
(http://www.mylittletools.net).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> My computer is part of the company computer network and connects to the
> internet through the company server which connects to the internet with an
> adsl modem installed on it.
> I have a sql server 2000 installed on my computer and I wish to access it
> from 'outside' through the internet and access its databases.
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...
>>Tomer,
>>I had a bit of trouble understanding what you are asking, I will recap.
>>You have a corporate network connected to the internet via a proxy
>>server (let's call this PROXY1). You want to "publish" your computer on
>>the internet, which resides behind PROXY1. What do you mean by
>>"publish"? Is it a web site, an FTP site, a database, remote desktop
>>connection, what?
>>You are running SQL Server on "my computer". Is this in the corporate
>>network or on the internet at home? Please clarify these points very
>>carefully (take a bit of time) as they will have a significant bearing
>>on the accuracy of the responses you will get.
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>Tomer wrote:
>>Hi,
>>I need to publish my computer on the internet which is on a company
> network.
>>in the network we have a server that connects to the internet and gives
>>internet access to all the company computers.
>>I'm running a sql server on my compuer and I need to access it through
> the
>>internet.
>>Also, I need to know how do I secure the connection to my
>>server/computer/company.
>>Any info on this would be great!!
>>
>
>|||Hi,
First thing, thanks alot for the info! I know that this is a problematic
issue in security, but I need to connect a pocket pc device with a gprs
modem directly to the sql server, and I'd rather not use a web service
application.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:OOIKLZsfEHA.1424@.tk2msftngp13.phx.gbl...
> Tomer,
> You will need to use NAT to allow your computer to act as a server. I
> would only do this sort of thing at home and never on a corporate network.
> On a corporate network you should have a demilitarised zone (DMZ) that
> allows incoming connections from the internet. I really do not recommend
> allow people from the public internet to connect directly to your LAN,
> you are asking for trouble. The DMZ should not be able to initiate
> connections to your LAN.
> I would go further and not even allow any form of direct access to a
> database server from the internet. Use a web server in a DMZ to connect
> to your db server (also in a separate DMZ) to serve information. If you
> need to manage a SQL Server from the internet you could use the web
> administrator (http://tinyurl.com/3cuzt) or even MyLittleTools
> (http://www.mylittletools.net).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
> > Hi,
> >
> > My computer is part of the company computer network and connects to the
> > internet through the company server which connects to the internet with
an
> > adsl modem installed on it.
> > I have a sql server 2000 installed on my computer and I wish to access
it
> > from 'outside' through the internet and access its databases.
> >
> >
> > "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> > news:eaZoMCsfEHA.140@.TK2MSFTNGP12.phx.gbl...
> >
> >>Tomer,
> >>
> >>I had a bit of trouble understanding what you are asking, I will recap.
> >>You have a corporate network connected to the internet via a proxy
> >>server (let's call this PROXY1). You want to "publish" your computer on
> >>the internet, which resides behind PROXY1. What do you mean by
> >>"publish"? Is it a web site, an FTP site, a database, remote desktop
> >>connection, what?
> >>
> >>You are running SQL Server on "my computer". Is this in the corporate
> >>network or on the internet at home? Please clarify these points very
> >>carefully (take a bit of time) as they will have a significant bearing
> >>on the accuracy of the responses you will get.
> >>--
> >>Mark Allison, SQL Server MVP
> >>http://www.markallison.co.uk
> >>
> >>Looking for a SQL Server replication book?
> >>http://www.nwsu.com/0974973602.html
> >>
> >>
> >>
> >>Tomer wrote:
> >>
> >>Hi,
> >>I need to publish my computer on the internet which is on a company
> >
> > network.
> >
> >>in the network we have a server that connects to the internet and gives
> >>internet access to all the company computers.
> >>I'm running a sql server on my compuer and I need to access it through
> >
> > the
> >
> >>internet.
> >>Also, I need to know how do I secure the connection to my
> >>server/computer/company.
> >>
> >>Any info on this would be great!!
> >>
> >>
> >
> >
> >|||OK,
What you need to do is NOT allow connections into your LAN. Create a DMZ
and place the SQL Server there. Do not allow the DMZ to initiate
connections into the LAN. Only allow connections from the LAN TO the DMZ.
Do not allow SQL Server to connect to anything else on your network.
Remember, if this machine is compromised, you could be in trouble. On
the firewall, only open one port to the SQL Server, and make sure this
is not 1433. Make it a high port number such as 56378 (or whatever).
Ensure SQL Server is listening on this port.
This will put you out of range of port scanners that are only looking
for common ports such as 139, 1433, etc, however will not protect you
from someone scanning every port on your machine, but then there are
intrusion detection tools available to protect you from this.
Another way to do this is to use a VPN tunnel from the client on the
internet, through a VPN server in a DMZ on your corporate network, and
then you can use the entire LAN. This might be easier to set up and
configure, then again it might not.
Whatever you do, do not allow direct connections from the public
internet, unencrypted into your LAN.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Tomer wrote:
> Hi,
> First thing, thanks alot for the info! I know that this is a problematic
> issue in security, but I need to connect a pocket pc device with a gprs
> modem directly to the sql server, and I'd rather not use a web service
> application.
>|||Thanks a bunch!! this helps alot
Tomer.
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u$IWGX4fEHA.632@.TK2MSFTNGP12.phx.gbl...
> OK,
> What you need to do is NOT allow connections into your LAN. Create a DMZ
> and place the SQL Server there. Do not allow the DMZ to initiate
> connections into the LAN. Only allow connections from the LAN TO the DMZ.
> Do not allow SQL Server to connect to anything else on your network.
> Remember, if this machine is compromised, you could be in trouble. On
> the firewall, only open one port to the SQL Server, and make sure this
> is not 1433. Make it a high port number such as 56378 (or whatever).
> Ensure SQL Server is listening on this port.
> This will put you out of range of port scanners that are only looking
> for common ports such as 139, 1433, etc, however will not protect you
> from someone scanning every port on your machine, but then there are
> intrusion detection tools available to protect you from this.
> Another way to do this is to use a VPN tunnel from the client on the
> internet, through a VPN server in a DMZ on your corporate network, and
> then you can use the entire LAN. This might be easier to set up and
> configure, then again it might not.
> Whatever you do, do not allow direct connections from the public
> internet, unencrypted into your LAN.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Tomer wrote:
> > Hi,
> >
> > First thing, thanks alot for the info! I know that this is a problematic
> > issue in security, but I need to connect a pocket pc device with a gprs
> > modem directly to the sql server, and I'd rather not use a web service
> > application.
> >

Publish scenario - how can this work?

Our current setup has a hand held device, a laptop and head office. The
field reps have the hand held and laptop and need to get and send data back
to head office. Merge Replication seems to be the answer and I was thinking
that the Head Office would publish to the Laptop and the Laptop would then
publish to the Hand Held. But SQL Server 2005 Express can only be a
Subscriber and not a Publisher.
The reason to do this is that only certain rows will be published to the
laptop (say 1 weeks work) and then only certain rows (say 1 or 2 days work)
will be published to the hand held.
Is there a way to accomplish this?
Here's how it breaks down:
Head Office = SQL Server 2005 Standard Edition
Laptop = SQL Server 2005 Express Edition
Hand Held = SQL Server 2005 Compact Edition
Thanks,
Richard.
You might want to look at RDA as the transit mechanism between Express and
the HandHelds.
Otherwise I would replicate from the Standard Edition publisher to the
handhelds.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Richard Wodabek" <rwodabek@.cogeco.ca> wrote in message
news:uocMysrNIHA.2268@.TK2MSFTNGP02.phx.gbl...
> Our current setup has a hand held device, a laptop and head office. The
> field reps have the hand held and laptop and need to get and send data
> back
> to head office. Merge Replication seems to be the answer and I was
> thinking
> that the Head Office would publish to the Laptop and the Laptop would then
> publish to the Hand Held. But SQL Server 2005 Express can only be a
> Subscriber and not a Publisher.
> The reason to do this is that only certain rows will be published to the
> laptop (say 1 weeks work) and then only certain rows (say 1 or 2 days
> work)
> will be published to the hand held.
> Is there a way to accomplish this?
> Here's how it breaks down:
> Head Office = SQL Server 2005 Standard Edition
> Laptop = SQL Server 2005 Express Edition
> Hand Held = SQL Server 2005 Compact Edition
> Thanks,
> Richard.
>
|||Thanks Hilary, RDA might work for us.
Any chance 2008 Express Edition will allow Publishing?
Richard.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uNmcUmzNIHA.292@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> You might want to look at RDA as the transit mechanism between Express and
> the HandHelds.
> Otherwise I would replicate from the Standard Edition publisher to the
> handhelds.
> --
> http://www.zetainteractive.com - Shift Happens!
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Richard Wodabek" <rwodabek@.cogeco.ca> wrote in message
> news:uocMysrNIHA.2268@.TK2MSFTNGP02.phx.gbl...
then
>

Publish reports to SQL 2000 RS using VS2005

We are migrating to SQL Server 2005 (and also RS shipped with SQL 2005) but
in the middle of the process we have still some servers still not upgraded
(and running SQL Server 2000 and RS2000).
Can we deploy reports to RS servers running SQL Server 2000 using Visual
Studio 2005? It seems we cannot becasue we receive the following error
message. Is any workaround to this or do we need to mantain a copy of both
RS2000 and RS2005 rdl files and deploy each group of them using VS2003 and
VS2005 respectively? This is somewhat repeat the same job twice, and might
lead to mistakes and differences between the same file of each version.
The error messages are in spanish but an approximated translation is
provided (It probably does not match the real error message in native
english).
Thanks a lot.
===================================
No se pudo establecer una conexión al servidor de informes
https://www.mydomain.com/ReportServer. (Diseñador de informes de Microsoft)
A connection to reports server at https://www.mydomain.com/ReportServer
could not be stablished (Microsoft Form Designer)
===================================
Error al intentar conectar con el servidor de informes. Compruebe la
información de conexión y que la versión del servidor de informes sea
compatible. (Microsoft.ReportingServices.Designer)
An error occurred while trying to connect to reports server. Check the
connection information and reports server version be compatable
(Microsoft.ReportingServices.Designer)
--
Ubicación del programa:
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException
e)
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
Item)
en
Microsoft.ReportDesigner.Project.ReportServiceClient.GetItemType(String
item)
en Microsoft.ReportDesigner.Project.ReportServiceClient.CheckAuthorized()
en
Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String
url)
en Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()
===================================
Error de la solicitud con el código de estado HTTP 404: Not Found.
(System.Web.Services)
--
Ubicación del programa:
en
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
en System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
en
Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetItemType(String
Item)
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
Item)You cannot deploy 2005 reports to RS 2000 server. However, you can deploy RS
2000 reports to a RS 2005 server. One caveat. When I did this I had a few
cases of some minor buggy behavior that went away when I converted to RS
2005. But, you might want to try that out.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jagb" <jagb@.NOSPAM.com> wrote in message
news:utyRqIwfGHA.2456@.TK2MSFTNGP04.phx.gbl...
> We are migrating to SQL Server 2005 (and also RS shipped with SQL 2005)
> but in the middle of the process we have still some servers still not
> upgraded (and running SQL Server 2000 and RS2000).
> Can we deploy reports to RS servers running SQL Server 2000 using Visual
> Studio 2005? It seems we cannot becasue we receive the following error
> message. Is any workaround to this or do we need to mantain a copy of both
> RS2000 and RS2005 rdl files and deploy each group of them using VS2003 and
> VS2005 respectively? This is somewhat repeat the same job twice, and might
> lead to mistakes and differences between the same file of each version.
> The error messages are in spanish but an approximated translation is
> provided (It probably does not match the real error message in native
> english).
> Thanks a lot.
> ===================================> No se pudo establecer una conexión al servidor de informes
> https://www.mydomain.com/ReportServer. (Diseñador de informes de
> Microsoft)
> A connection to reports server at https://www.mydomain.com/ReportServer
> could not be stablished (Microsoft Form Designer)
> ===================================> Error al intentar conectar con el servidor de informes. Compruebe la
> información de conexión y que la versión del servidor de informes sea
> compatible. (Microsoft.ReportingServices.Designer)
> An error occurred while trying to connect to reports server. Check the
> connection information and reports server version be compatable
> (Microsoft.ReportingServices.Designer)
> --
> Ubicación del programa:
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException
> e)
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
> Item)
> en
> Microsoft.ReportDesigner.Project.ReportServiceClient.GetItemType(String
> item)
> en
> Microsoft.ReportDesigner.Project.ReportServiceClient.CheckAuthorized()
> en
> Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String
> url)
> en
> Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()
> ===================================> Error de la solicitud con el código de estado HTTP 404: Not Found.
> (System.Web.Services)
> --
> Ubicación del programa:
> en
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> en System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> en
> Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetItemType(String
> Item)
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
> Item)
>

Publish Reports Server to Internet

Hi all,
I have an external IP for my server and I tried to connect it from out side,
I notice that the link address appear on Status bar is my localhost's name
link ... and that's why it can be accessed to view reports. It just work if I
re-config my IP setting following external IP. Who can expalin me or show me
some addresses to study more about this problem ?
--
Thnx lots,
NgocYour local machine has its IP address and the server has its IP address
accessible from the Internet? Assuming you have configured security so that
the server is accessible from outside, you just need to do
http://<serverIPaddress>/Reports or https://<serverIPaddress>/Reports, right?
If you are doing http://<yourmachine>/Reports, then you will see the local
report server, unless you have used rsconfig.exe to point your local server
to the external server URL. Books Online has details on using rsconfig.exe.
Charles Kangai, MCDBA, MCT
"Phi Ngoc" wrote:
> Hi all,
> I have an external IP for my server and I tried to connect it from out side,
> I notice that the link address appear on Status bar is my localhost's name
> link ... and that's why it can be accessed to view reports. It just work if I
> re-config my IP setting following external IP. Who can expalin me or show me
> some addresses to study more about this problem ?
> --
> Thnx lots,
> Ngoc|||I am having the same problem where I go here http://(fqdn.external.name)
/Reports
The reports are viewable externally, but if I try to export them it reverts
to the computer name (Which happens to be MISERY) like this
http://misery/Reports/Pages/Reports.aspx..etc.etc
Does anyone know how to change this?
Thanks.
--
Message posted via http://www.sqlmonster.com|||Open the RSWebApplication.config file and check the URL inside the
<ReportServerURL> element. Do the same with RSReportServer.config file. The
files are located in the folders <SQL Server Installation>\Reporting
Services\ReportManager and <SQL Server Installation>\Reporting
Services\ReportServer, respectively.
Charles Kangai, MCDBA, MCT
"David Benedict via SQLMonster.com" wrote:
> I am having the same problem where I go here http://(fqdn.external.name)
> /Reports
> The reports are viewable externally, but if I try to export them it reverts
> to the computer name (Which happens to be MISERY) like this
> http://misery/Reports/Pages/Reports.aspx..etc.etc
> Does anyone know how to change this?
> Thanks.
> --
> Message posted via http://www.sqlmonster.com
>

publish report

Hello,

I have create a web base project that will programmatically publish report into report server 2005.

But when i run the code, i need to create a shared data source and set the DataSourceReference.

Is there any ways else so that i no need to create a shared data source but still can publish the report in report server 2005 using custom data source?

Thanks.

You don't have to use shared datasource. You can just define a report specific datasource, in which case, all the datasource properties are embedded in the rdl. http://msdn2.microsoft.com/en-us/library/ms159165.aspx

Publish custom assembly with query

My custom assembly works in design mode but when i publish it :

- function without query work well.

- function with query return an error (#Error).

The assembly was copied in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin

What can i do the use query in my custom assembly.

Thanks for all your answers.

Have you looked at this article.

http://support.microsoft.com/default.aspx?scid=kb;en-us;842419

Problems with custom assemblies are usually related to not granting the correct permissions to the assembly in the config files.

Publish between servers

Is it possible to publish a report from a DEV reporting server to a
PRODUCTION reporting server?
We would like our developer to deploy to the DEV server and then
someone publish it to production
gertYou can use RSScripter to do this
http://www.sqldbatips.com/showarticle.asp?ID=62
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Gert Conradie" <gert.conradie@.gmail.com> wrote in message
news:1125402536.289327.24680@.f14g2000cwb.googlegroups.com...
> Is it possible to publish a report from a DEV reporting server to a
> PRODUCTION reporting server?
> We would like our developer to deploy to the DEV server and then
> someone publish it to production
> gert
>|||Perfect, really really handy!
Wish list: Specify destination server so that one dont have to run the
bat file in two step process. But still as it is - really hande.
Thanks.
gert
Jasper Smith wrote:
> You can use RSScripter to do this
> http://www.sqldbatips.com/showarticle.asp?ID=62
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Gert Conradie" <gert.conradie@.gmail.com> wrote in message
> news:1125402536.289327.24680@.f14g2000cwb.googlegroups.com...
> > Is it possible to publish a report from a DEV reporting server to a
> > PRODUCTION reporting server?
> >
> > We would like our developer to deploy to the DEV server and then
> > someone publish it to production
> >
> > gert
> >

Publish A Report Services Report to SharePoint

OK... I'm running out of things to try.

I have SQL Server 2005 SP2 installed and Reporting Services Addin configured. I am trying to publish a report from BIDS to SharePoint... but a box continues to pop up asking me for credencials.

What am I doing wrong? I have reviewed all the web.config files as per an earlier post referenced, but I only see one entry in the config file for the location tag. However, I did see this tag in two config files... not certain if that is something I should be concerned with?

I'd really like to just get a sample report up on the Sharepoint Server so I can move forward.

Can anyone help?

You can always just upload the .RDL file directly into SharePoint using the SharePoint web UI. When RS integrates with SharePoint, we tell SharePoint to handle .RDL files as Report Server items, and it doesn't really matter whether they get into SharePoint through Report Designer, or through SharePoint web UI.

I'm afraid I can't help with the Report Designer issue. I'll pass this on to someone who might know about it.

|||Please check Inetpub\wwwroot\wss\VirtualDirectories\80\web.config|||

What am I looking for when I go to Inetpub\wwwroot\wss\VirtualDirectories\80\web.config?

It does have one entry for location path=" _vti_bin...." as previously mentioned, a number of the web config files have this entry in it... but only once per file.

And just to clarify... I am using BIDS trying to deploy the report. The version of Visual Studio is: 8.0.50727.42.

|||I did that and surprisingly it worked... how does the report connect to the database? I did not upload or create a datasource? Well... actually I had manually created one in SharePoint in another library, but subsequently deleted it. The report still runs?|||Actually... I'll answer my own question... the first report used a custom data source... so that is why it worked. The second used a shared data source... it failed until I created the shared datasource|||

I've been running into this, too. Brian Welcker's blog solved it.

http://blogs.msdn.com/bimusings/archive/2007/02/07/reporting-services-login-dialog-appears-when-deploying-to-moss-wss.aspx

Publications... Im a beginner

Hi people
I m just beginning with SQL Server 2005 Express Edition and I need some help.
I want to have a small database in a server (I've already created) and it will be used to synchronize it with PDAs (Pocket PC 2002) through MS SQL Server CE 2.0.
I have "SQL Server 2005 Express Edition" and "SQL Server Management Studio Express", and I don′t know how to create a publication of my database (I need a merge publication). I think it is necessary in order to make replications.
Any answer, idea or suggestion would be welcome.
Thanks in advance.
Best regards.
Ok I found this at http://msdn2.microsoft.com/en-us/library/ms165686.aspx
SQL Server Express cannot serve as a Publisher or Distributor.
I don't want to (or can not) pay a SQL Server license so... I will try to do it through web services.
ciao!

Publications with Pending Status

I am receiving the following errors in the event viewer:
Application log
SubSystem Message - Job 'BOS01-253-USICOAL-1'
(0x5E7E64490BAF924BB783E4C4F54C3E19), step 2 - SQL Server Agent could not
access the replication agent. Use the DCOMCNFG utility to confirm that the
SQL Server Agent Windows account has permissions to launch the replication
agent.
system log
Access denied attempting to launch a DCOM Server. The server is:
{08B0B2D9-3FB3-11D3-A4DE-00C04F610189}
The user is SYSTEM/NT AUTHORITY, SID=S-1-5-18.
I am running windows 2003 Server with XP Embedded clients, replication is
configured as push jobs from the distributer.
are you using remote agent activation?
If not, run DCOMCNFG to determine exactly where your merge agent is running.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:88C3A06B-CA0A-41D3-9100-4DD33BB79CA5@.microsoft.com...
>I am receiving the following errors in the event viewer:
> Application log
> SubSystem Message - Job 'BOS01-253-USICOAL-1'
> (0x5E7E64490BAF924BB783E4C4F54C3E19), step 2 - SQL Server Agent could not
> access the replication agent. Use the DCOMCNFG utility to confirm that the
> SQL Server Agent Windows account has permissions to launch the replication
> agent.
> system log
> Access denied attempting to launch a DCOM Server. The server is:
> {08B0B2D9-3FB3-11D3-A4DE-00C04F610189}
> The user is SYSTEM/NT AUTHORITY, SID=S-1-5-18.
> I am running windows 2003 Server with XP Embedded clients, replication is
> configured as push jobs from the distributer.
|||I don't thinks so, where do I check?
I have used DCOMCNFG and the merge agent is running locally.
Thanks
Mark
"Hilary Cotter" wrote:

> are you using remote agent activation?
> If not, run DCOMCNFG to determine exactly where your merge agent is running.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:88C3A06B-CA0A-41D3-9100-4DD33BB79CA5@.microsoft.com...
>
>
|||Not sure if we are using remote agent activation, where do I check?
I have checked in DCOMCNFG and the merge agent is running locally.
thanks
Mark
"Hilary Cotter" wrote:

> are you using remote agent activation?
> If not, run DCOMCNFG to determine exactly where your merge agent is running.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:88C3A06B-CA0A-41D3-9100-4DD33BB79CA5@.microsoft.com...
>
>
|||script out your publication and post it here.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:B3C9C4EA-A8EC-44F1-AFA5-FBF2CB721251@.microsoft.com...[vbcol=seagreen]
> I don't thinks so, where do I check?
> I have used DCOMCNFG and the merge agent is running locally.
> Thanks
> Mark
> "Hilary Cotter" wrote:
running.[vbcol=seagreen]
not[vbcol=seagreen]
the[vbcol=seagreen]
replication[vbcol=seagreen]
is[vbcol=seagreen]
|||Also check the Security tab for Microsoft SQL Server Replication Merge Agent
8.0 Properties, and verify that for the default Launch Permissions, the
everyone group has special access.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:7B60532F-1088-4BD9-9061-8BA6A7A044A7@.microsoft.com...[vbcol=seagreen]
> Not sure if we are using remote agent activation, where do I check?
> I have checked in DCOMCNFG and the merge agent is running locally.
> thanks
> Mark
> "Hilary Cotter" wrote:
running.[vbcol=seagreen]
not[vbcol=seagreen]
the[vbcol=seagreen]
replication[vbcol=seagreen]
is[vbcol=seagreen]
|||Here is one of the publications:
-- Enabling the replication database
use master
GO
exec sp_replicationdboption @.dbname = N'USICOAL', @.optname = N'publish',
@.value = N'true'
GO
use [USICOAL]
GO
-- Adding the transactional publication
exec sp_addpublication @.publication = N'PUB_ITEM', @.restricted = N'false',
@.sync_method = N'native', @.repl_freq = N'continuous', @.description =
N'Transactional publication of item data (PLU)', @.status = N'active',
@.allow_push = N'true', @.allow_pull = N'true', @.allow_anonymous = N'false',
@.enabled_for_internet = N'false', @.independent_agent = N'false',
@.immediate_sync = N'false', @.allow_sync_tran = N'false', @.autogen_sync_procs
= N'false', @.retention = 0, @.allow_queued_tran = N'false',
@.snapshot_in_defaultfolder = N'true', @.compress_snapshot = N'false',
@.ftp_port = 21, @.ftp_login = N'anonymous', @.allow_dts = N'false',
@.allow_subscription_copy = N'false', @.add_to_active_directory = N'false',
@.logreader_job_name = N'BOS01-253-USICOAL-1'
exec sp_addpublication_snapshot @.publication = N'PUB_ITEM',@.frequency_type =
4, @.frequency_interval = 1, @.frequency_relative_interval = 1,
@.frequency_recurrence_factor = 0, @.frequency_subday = 8,
@.frequency_subday_interval = 1, @.active_start_date = 0, @.active_end_date = 0,
@.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.snapshot_job_name = N'BOS01-253-USICOAL-PUB_ITEM-3'
GO
exec sp_grant_publication_access @.publication = N'PUB_ITEM', @.login = N'admin'
GO
exec sp_grant_publication_access @.publication = N'PUB_ITEM', @.login =
N'BUILTIN\Administrators'
GO
exec sp_grant_publication_access @.publication = N'PUB_ITEM', @.login =
N'distributor_admin'
GO
exec sp_grant_publication_access @.publication = N'PUB_ITEM', @.login = N'sa'
GO
-- Adding the transactional articles
exec sp_addarticle @.publication = N'PUB_ITEM', @.article =
N'ADDITIONAL_INFO', @.source_owner = N'dbo', @.source_object =
N'ADDITIONAL_INFO', @.destination_table = N'ADDITIONAL_INFO', @.type =
N'logbased', @.creation_script = null, @.description = null, @.pre_creation_cmd
= N'drop', @.schema_option = 0x00000000000000F3, @.status = 16,
@.vertical_partition = N'false', @.ins_cmd = N'CALL sp_MSins_ADDITIONAL_INFO',
@.del_cmd = N'CALL sp_MSdel_ADDITIONAL_INFO', @.upd_cmd = N'MCALL
sp_MSupd_ADDITIONAL_INFO', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article = N'DEPT_SELL_RULE',
@.source_owner = N'dbo', @.source_object = N'DEPT_SELL_RULE',
@.destination_table = N'DEPT_SELL_RULE', @.type = N'logbased', @.creation_script
= null, @.description = null, @.pre_creation_cmd = N'drop', @.schema_option =
0x00000000000000F3, @.status = 16, @.vertical_partition = N'false', @.ins_cmd =
N'CALL sp_MSins_DEPT_SELL_RULE', @.del_cmd = N'CALL sp_MSdel_DEPT_SELL_RULE',
@.upd_cmd = N'MCALL sp_MSupd_DEPT_SELL_RULE', @.filter = null, @.sync_object =
null, @.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article = N'ITEM_GROUP',
@.source_owner = N'dbo', @.source_object = N'ITEM_GROUP', @.destination_table =
N'ITEM_GROUP', @.type = N'logbased', @.creation_script = null, @.description =
null, @.pre_creation_cmd = N'drop', @.schema_option = 0x00000000000000F3,
@.status = 16, @.vertical_partition = N'false', @.ins_cmd = N'CALL
sp_MSins_ITEM_GROUP', @.del_cmd = N'CALL sp_MSdel_ITEM_GROUP', @.upd_cmd =
N'MCALL sp_MSupd_ITEM_GROUP', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article =
N'ITEM_GROUP_ITEM', @.source_owner = N'dbo', @.source_object =
N'ITEM_GROUP_ITEM', @.destination_table = N'ITEM_GROUP_ITEM', @.type =
N'logbased', @.creation_script = null, @.description = null, @.pre_creation_cmd
= N'drop', @.schema_option = 0x00000000000000F3, @.status = 16,
@.vertical_partition = N'false', @.ins_cmd = N'CALL sp_MSins_ITEM_GROUP_ITEM',
@.del_cmd = N'CALL sp_MSdel_ITEM_GROUP_ITEM', @.upd_cmd = N'MCALL
sp_MSupd_ITEM_GROUP_ITEM', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article =
N'ITEM_GRP_ADDL_INFO', @.source_owner = N'dbo', @.source_object =
N'ITEM_GRP_ADDL_INFO', @.destination_table = N'ITEM_GRP_ADDL_INFO', @.type =
N'logbased', @.creation_script = null, @.description = null, @.pre_creation_cmd
= N'drop', @.schema_option = 0x00000000000000F3, @.status = 16,
@.vertical_partition = N'false', @.ins_cmd = N'CALL
sp_MSins_ITEM_GRP_ADDL_INFO', @.del_cmd = N'CALL sp_MSdel_ITEM_GRP_ADDL_INFO',
@.upd_cmd = N'MCALL sp_MSupd_ITEM_GRP_ADDL_INFO', @.filter = null, @.sync_object
= null, @.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article = N'PLU',
@.source_owner = N'dbo', @.source_object = N'PLU', @.destination_table = N'PLU',
@.type = N'logbased', @.creation_script = null, @.description = null,
@.pre_creation_cmd = N'drop', @.schema_option = 0x00000000000000F3, @.status =
16, @.vertical_partition = N'false', @.ins_cmd = N'CALL sp_MSins_PLU', @.del_cmd
= N'CALL sp_MSdel_PLU', @.upd_cmd = N'MCALL sp_MSupd_PLU', @.filter = null,
@.sync_object = null, @.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article = N'PLU_PRICE',
@.source_owner = N'dbo', @.source_object = N'PLU_PRICE', @.destination_table =
N'PLU_PRICE', @.type = N'logbased', @.creation_script = null, @.description =
null, @.pre_creation_cmd = N'drop', @.schema_option = 0x00000000000000F3,
@.status = 16, @.vertical_partition = N'false', @.ins_cmd = N'CALL
sp_MSins_PLU_PRICE', @.del_cmd = N'CALL sp_MSdel_PLU_PRICE', @.upd_cmd =
N'MCALL sp_MSupd_PLU_PRICE', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article =
N'POS_ID_PLU_CODE', @.source_owner = N'dbo', @.source_object =
N'POS_ID_PLU_CODE', @.destination_table = N'POS_ID_PLU_CODE', @.type =
N'logbased', @.creation_script = null, @.description = null, @.pre_creation_cmd
= N'drop', @.schema_option = 0x00000000000000F3, @.status = 16,
@.vertical_partition = N'false', @.ins_cmd = N'CALL sp_MSins_POS_ID_PLU_CODE',
@.del_cmd = N'CALL sp_MSdel_POS_ID_PLU_CODE', @.upd_cmd = N'MCALL
sp_MSupd_POS_ID_PLU_CODE', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
exec sp_addarticle @.publication = N'PUB_ITEM', @.article =
N'POS_ITEM_ADDL_INFO', @.source_owner = N'dbo', @.source_object =
N'POS_ITEM_ADDL_INFO', @.destination_table = N'POS_ITEM_ADDL_INFO', @.type =
N'logbased', @.creation_script = null, @.description = null, @.pre_creation_cmd
= N'drop', @.schema_option = 0x00000000000000F3, @.status = 16,
@.vertical_partition = N'false', @.ins_cmd = N'CALL
sp_MSins_POS_ITEM_ADDL_INFO', @.del_cmd = N'CALL sp_MSdel_POS_ITEM_ADDL_INFO',
@.upd_cmd = N'MCALL sp_MSupd_POS_ITEM_ADDL_INFO', @.filter = null, @.sync_object
= null, @.auto_identity_range = N'false'
GO
-- Adding the transactional subscription
exec sp_addsubscription @.publication = N'PUB_ITEM', @.article = N'all',
@.subscriber = N'TILL01-253', @.destination_db = N'USICOAL', @.sync_type =
N'automatic', @.update_mode = N'read only', @.offloadagent = 0,
@.dts_package_location = N'distributor'
GO
-- Adding the transactional subscription
exec sp_addsubscription @.publication = N'PUB_ITEM', @.article = N'all',
@.subscriber = N'TILL02-253', @.destination_db = N'USICOAL', @.sync_type =
N'automatic', @.update_mode = N'read only', @.offloadagent = 0,
@.dts_package_location = N'distributor'
GO
-- Adding the transactional subscription
exec sp_addsubscription @.publication = N'PUB_ITEM', @.article = N'all',
@.subscriber = N'TILL03-253', @.destination_db = N'USICOAL', @.sync_type =
N'automatic', @.update_mode = N'read only', @.offloadagent = 0, @.offloadserver
= N'<NULL>', @.dts_package_location = N'distributor'
GO
-- Adding the transactional subscription
exec sp_addsubscription @.publication = N'PUB_ITEM', @.article = N'all',
@.subscriber = N'TILL04-253', @.destination_db = N'USICOAL', @.sync_type =
N'automatic', @.update_mode = N'read only', @.offloadagent = 0, @.offloadserver
= N'TILL04-253', @.dts_package_location = N'distributor'
GO
"Hilary Cotter" wrote:

> script out your publication and post it here.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:B3C9C4EA-A8EC-44F1-AFA5-FBF2CB721251@.microsoft.com...
> running.
> not
> the
> replication
> is
>
>

Publications

Can someone tell me about creating a publication?From BOL:

Publication
A publication is a collection of one or more articles from one database. This grouping of multiple articles makes it easier to specify a logically related set of data and database objects that you want to replicate together.

Article
An article is a table of data, a partition of data, or a database object that is specified for replication. An article can be an entire table, certain columns (using a vertical filter), certain rows (using a horizontal filter), a stored procedure or view definition, the execution of a stored procedure, a view, an indexed view, or a user-defined function.

HTH|||Thanks. I can't see too much in my books.|||Use BOL (Books online) as much as you can, it really helps on definiton type things (and more) if you don't have it you can download it here:

http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp?

Publication w/o logreader agent. Is it possible?

Hi,
Is it possible to create a publication without creating a logreader agent at
the same time? I'm on MS SQL Server 2000 SP3a.
-- Many thanks, Oskar
Oskar - if you are talking about transactional replication, this is an
integral part of the functioning. I'm interested in why would you like to
avoid the logreader agent?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Yes, transactional is what I am talking about. I am interested in this
because I want to have development databases published but I do not want to
have any real replication going on there. This is needed because we must have
identical "change management" in development and production environments.
Looks like I have partly solved this problem by making each development
server a publisher and a distributor, and regenerating the publication from a
script. I even could do without the snapshot agent, but getting rid of the
logreader seems to be tricky, if not impossible.
-- Thanks, Oskar
"Paul Ibison" wrote:

> Oskar - if you are talking about transactional replication, this is an
> integral part of the functioning. I'm interested in why would you like to
> avoid the logreader agent?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Oskar,
don't know if this helps, but until the snapshot has run, the log reader
isn't moving any commands to the distribution database. To prevent it
parsing the transaction log you could simply stop it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||That's exactly what I did. I just don't like to stop it manually everytime
the development database gets refreshed - its job name and id changes at
every such refreshing.
-- Oskar
"Paul Ibison" wrote:

> Oskar,
> don't know if this helps, but until the snapshot has run, the log reader
> isn't moving any commands to the distribution database. To prevent it
> parsing the transaction log you could simply stop it.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||I'd add a piece of code at the end of the script which stops and disables
the job - that way you don't need to worry about it afterwards.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Publication takes record off subscriber

When I synch my subscriber back to my maste. A record I created on the
subscriber is now on the master but it is not also on the subscriber
like it should be. Any ideas? Everything seems to be in order.
Never mind. Those above me decided to add filters without telling me.
Thanks for taking the time to read this.
On Thu, 28 Apr 2005 16:09:14 -0600, Shane Lim <gslim@.blizzardice.com>
wrote:

>When I synch my subscriber back to my maste. A record I created on the
>subscriber is now on the master but it is not also on the subscriber
>like it should be. Any ideas? Everything seems to be in order.

publication status

Here is what i get under sp_helpmergepublication :
status : 1
retention : 14
sync_mode : 0
allow_push : 1
allow_pull : 1
allow_anonymous : 1 <--
centralized_conflicts : 1
prority : 100.0
snapshot_ready : 0
publication_type : 0
pubid : (some value)
snapshot_jobid : (some value)
enabled_for_internet : 0
dynamic_filters : 0
has_subscription : 1
(...)
conflict_retention : 14
keep_partition_changes : 0
allow_subscription_copy : 0
allow_synctoalternate : 0
validate_subscriber_info : NULL
backward_comp_level : 40
publish_to_activeddirectory : 0
max_concurrent_merge : 0
max_concurrent_dynamic_snapshots : 0
"Hilary Cotter" wrote:
[vbcol=seagreen]
> If your publication is configured for anonymous subscribers the snapshot
> should always be ready and you should not have this problem.
> the
Is your subscriber anonymous or named?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nevrose" <Nevrose@.discussions.microsoft.com> wrote in message
news:F9C8C56F-6CBF-47B0-87E0-E2DDC9B3520D@.microsoft.com...[vbcol=seagreen]
> Here is what i get under sp_helpmergepublication :
> status : 1
> retention : 14
> sync_mode : 0
> allow_push : 1
> allow_pull : 1
> allow_anonymous : 1 <--
> centralized_conflicts : 1
> prority : 100.0
> snapshot_ready : 0
> publication_type : 0
> pubid : (some value)
> snapshot_jobid : (some value)
> enabled_for_internet : 0
> dynamic_filters : 0
> has_subscription : 1
> (...)
> conflict_retention : 14
> keep_partition_changes : 0
> allow_subscription_copy : 0
> allow_synctoalternate : 0
> validate_subscriber_info : NULL
> backward_comp_level : 40
> publish_to_activeddirectory : 0
> max_concurrent_merge : 0
> max_concurrent_dynamic_snapshots : 0
>
> "Hilary Cotter" wrote:
obtain[vbcol=seagreen]
|||Anonymous.
I have 2 suscribers.
Here is what i've got from sp_helpmergepullsubscription for both of them :
status 0 = All jobs are waiting to start
subscriber_type 3 = Anonymous
subscription_type 2 = Anonymous
priority 0.0
sync_type 1 = Automatic
enabled_for_synmgr 1
last_updated NULL
publisher_login NULL
publisher_password (nothing here)
publisher_security_mode 1 = Windows Authentication
distributor_login sa
distributor_password (nothing here)
distributor_security_mode 1 = Windows Authentication
use_ftp 0 = Subscription is not using FTP
offload_agent 0 = The agent cannot be remotely activated
use_interactive_resolver 0 = The interactive resolver is not used
dynamic_snapshot_location NULL
last_sync_status NULL (?, should be int)
last_sync_summary NULL
"Hilary Cotter" wrote:

> Is your subscriber anonymous or named?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Nevrose" <Nevrose@.discussions.microsoft.com> wrote in message
> news:F9C8C56F-6CBF-47B0-87E0-E2DDC9B3520D@.microsoft.com...
> obtain
>
>

Publication script error

Hello,
I am creating Publication through sql script. I have created Publication on
my machine using wizard and after that I created the script for the
publication. When I am running this script on another sql server it is giving
me an error saying Distributor not configured properly. What I need to do to
remove this error? Can this problem be solved by running some sql script?
Becoz I am creating all this through Installshield. So I need the script of
this. Please Help...
Sounds like replication is not installed on this server. Go to tools,
replication, enable replication and follow the prompts accepting the
defaults.
"Subin" <Subin@.discussions.microsoft.com> wrote in message
news:567DC900-D413-4769-916C-E24FF90B9A0E@.microsoft.com...
> Hello,
> I am creating Publication through sql script. I have created Publication
> on
> my machine using wizard and after that I created the script for the
> publication. When I am running this script on another sql server it is
> giving
> me an error saying Distributor not configured properly. What I need to do
> to
> remove this error? Can this problem be solved by running some sql script?
> Becoz I am creating all this through Installshield. So I need the script
> of
> this. Please Help...

publication retention to increase, how to avoid missing metadata after cleanup

I currently use 7 days for subscription expiration setting for my two merge publications, which will cause metadata to clean up very 7 days. Now I need to increase the retention period to be 14 days. How I can avoid missing metadata after cleanup? Microsoft ms151188 (http://msdn2.microsoft.com/en-us/library/ms151188.aspx) warns that publisher may not have enough metadata, which may lead to non-convergence. I want to change this setting without causing any data loss.

Thanks much,

I don't think changing retention setting will cause metadata loss. Of course if you want to be 100% sure, quiesce the system and then change the setting.

Publication Problem

Hello,
I want to Create Publication with the Wizard but i always have a great
problem: After i click on okay on the Specify Snapshot Folder i always get
the following error:
"SQL Server Enterprise Manager could not retrieve information about the
Distributor of the database. Error 1038: Cannot use empty object or column
names. Use a single space if necessary."
And when i click on okay and the "Choose Publication Database" screen
appears i cannnot choose any database because in there do not appear any
databases.
What went wrong here?
Can anybody please help me here?
regards
patrick
PS: When i want to create a new Table for a Database a similar error occurs:
An unexpected error happened during this operation.
[Microsoft SQL-DMO (ODBC SQLState: 42000) - Cannot use empty object or
column names. Use a single space if necessary.
Maybe this could help to explain me what went wrong in my Enterprise Manager
that the Publication does not work correctly?
Hello,
I installed the Microsoft SQL Server 2000 on my machine once more and
fortunately the Publicaten worked. I did it like it is quoted in your posted
doc-file and on this
<a
href=http://msdn.microsoft.com/SQL/SQLCE/default.aspx?pull=/msdnmag/issues/03/09/datapoints/default.aspx> ReplicationExample
site, because i want to go through the sample of this site.
But it were to good to be true if all would be work, when i deploy the
sample application from this site on the Emulator and presses the
Synch-Button of the application, the following error occurs in a message box
on the display:
Error #1 of 1
Error Code: -2147012867
Message: A request to send data to the computer running IIS has failed. For
more information, see HRESULT.[,,,,]
Minor Err.: 28037
Source: Microsoft SQL Server 2000 Windows CE Edition.
Do know what went wrong here or do i have forgotten anything during the
Create Virtual Directory Wizard or the Publication Wizard or anything else?
Hopefully you are willing to help me again, because i do not simply look
through it.
regards
patrick
PS: I did all as i quoted it in the previous posting and once more my IIS,
SQL Server 2000 and VS.NET are all on the same machine.

Publication not enabled to use an independent agent

I've created a snapshot replication between 2 databases on 2 different
servers to run once a day. The snapshot has worked but when the
distribution job runs it fails within a few seconds. I've looked at the
job history and the following error message is recorded:
Publication 'EmailDB' is not enabled to use an independent agent. The
step failed.
I think this may be because I've defined the publication so that
anonymous pull subscriptions are not allowed. If not does anyone know
what the problem could be. If it is how do I alter the publication so
that they are allowed - the option doesn't appear to be changeable with
the publication properties window in EM.
TIA
Laurence Breeze
drop your subscriptions and try this
sp_changepublication 'pubs4','independent_agent','true'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Breeze" <laurence_breeze@.yahoo.co.uk> wrote in message
news:4289AD77.5070305@.yahoo.co.uk...
> I've created a snapshot replication between 2 databases on 2 different
> servers to run once a day. The snapshot has worked but when the
> distribution job runs it fails within a few seconds. I've looked at the
> job history and the following error message is recorded:
> Publication 'EmailDB' is not enabled to use an independent agent. The
> step failed.
> I think this may be because I've defined the publication so that
> anonymous pull subscriptions are not allowed. If not does anyone know
> what the problem could be. If it is how do I alter the publication so
> that they are allowed - the option doesn't appear to be changeable with
> the publication properties window in EM.
> TIA
> Laurence Breeze
>

publication include new tables created automatically?

Hi All,
I have a merge replication on a SQL 2000 database to a remote site.
I have selected "publish all" in publication properties. Now if I a new
table is created, does it automatically runs the snapshot agent and include
that table in to the table schema?
Thanks in advance for the answer... :-)
Maani...
Using sp_addmergearticle followed by running the snapshot agent and merge
agents should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Publication has expired

I have setup transaction replication using seperate server for distribution
box.
Server A - Publisher (Win2003, SQL2000 SP818)
Server B - Distributor (Win2003, SQL2000 SP818)
Server C - Subscriber1 (Win2003 and SQL2000 SP818)
Server D - Subscriber2 (Win2003 and SQL2000 SP818)
Server E - Subscriber3 (Win2000, SQL2000 SP818)
Server A has 3 publishers and each publisher has more than 10 articles, one
of them we use it for monitoring replication by update a datetime column from
sql job.
The trans. replication are running fine execpt the subscriber3. This
subsciber always get sthe subscription expires errors, but the monitor
article does get updated. And the wired thing is the replication monitor on
the distribution server shows that the agent is in suspect and no reponse
within 10 min after each snapshot/initation.
I did query the MSDistribution_History and there is only one row which the
date I ran the snspshot. All the retention and history period are default.
Does anyone knows that it is Win2003 to Win2000 issue or something else.
Thanks in advance
This guy expired prematurely because your history retention is less than
your publication retention. Bump this setting up to your publication
retention, and be highly proactive about sensing when this guy has dropped
off the network for more than 1 day.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"kc" <kc@.discussions.microsoft.com> wrote in message
news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> I have setup transaction replication using seperate server for
distribution
> box.
> Server A - Publisher (Win2003, SQL2000 SP818)
> Server B - Distributor (Win2003, SQL2000 SP818)
> Server C - Subscriber1 (Win2003 and SQL2000 SP818)
> Server D - Subscriber2 (Win2003 and SQL2000 SP818)
> Server E - Subscriber3 (Win2000, SQL2000 SP818)
> Server A has 3 publishers and each publisher has more than 10 articles,
one
> of them we use it for monitoring replication by update a datetime column
from
> sql job.
> The trans. replication are running fine execpt the subscriber3. This
> subsciber always get sthe subscription expires errors, but the monitor
> article does get updated. And the wired thing is the replication monitor
on
> the distribution server shows that the agent is in suspect and no reponse
> within 10 min after each snapshot/initation.
> I did query the MSDistribution_History and there is only one row which the
> date I ran the snspshot. All the retention and history period are
default.
> Does anyone knows that it is Win2003 to Win2000 issue or something else.
> Thanks in advance
|||In my case, the monitor article in the subscriber had same time as the
publisher when it was mark for expiration. Therefore it is not a network
issue.
By default, the hsitory rentention is 48 hrs and transaction rentention is
72 hrs, so I don't understand what do you mean that I need to bump the
setting up?
Thanks
KC
"Hilary Cotter" wrote:

> This guy expired prematurely because your history retention is less than
> your publication retention. Bump this setting up to your publication
> retention, and be highly proactive about sensing when this guy has dropped
> off the network for more than 1 day.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "kc" <kc@.discussions.microsoft.com> wrote in message
> news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> distribution
> one
> from
> on
> default.
>
>

Publication Filter Clause changes

Hello,
I've merge replication set between SQL Server 2000 & SQL CE.
Whenever I try to add filter clause to the existing publication, it gives
error mentioning the column name used in the filter clause.
Ex. Let's say I've 5 publications - Pub1, Pub2, Pub3, Pub4, Pub5.
If I add filter clause say 'Employee_Status <> 0' then it throws the error
as 'Invalid Column Name 'Employee_Status'' even if that column is present in
the table.
But, if I drop all publications (pub1 to pub5), then the whole thing works
perfectly fine. But it is not feasible to drop ALL publications (even the
ones not related to this change) to change the filter clause of 1 article for
just 1 publication. Is there any way out other than dropping the publications?
Thanks in advance for help.
Regards,
Shweta
exactly how are you deploying your publication to your SQL CE clients?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Shweta" <Shweta@.discussions.microsoft.com> wrote in message
news:697E3FFF-8A77-4FC1-ABCE-747679F84DF3@.microsoft.com...
> Hello,
> I've merge replication set between SQL Server 2000 & SQL CE.
> Whenever I try to add filter clause to the existing publication, it gives
> error mentioning the column name used in the filter clause.
> Ex. Let's say I've 5 publications - Pub1, Pub2, Pub3, Pub4, Pub5.
> If I add filter clause say 'Employee_Status <> 0' then it throws the error
> as 'Invalid Column Name 'Employee_Status'' even if that column is present
in
> the table.
> But, if I drop all publications (pub1 to pub5), then the whole thing works
> perfectly fine. But it is not feasible to drop ALL publications (even the
> ones not related to this change) to change the filter clause of 1 article
for
> just 1 publication. Is there any way out other than dropping the
publications?
> Thanks in advance for help.
> Regards,
> Shweta

Publication falls to inactive

Hi all
We are using a pull publication what works well. After a time, maybe next
day, the publication must be reinitialized again.
The duration property of the publication does not define a final date. I
could not find other properties controlling the activation state.
Is this a security issue why a publication falls to inactive?
Thanks for help, Jan
Pls have a look at the retention period for the publication, the transactions
and the history retention. One or more of these is likely to be being
exceeded.
Paul Ibison

Publication error ODBCBCP/Driver version mismatch

Hi.
I'm trying to setup a publication but I received an error:
The process could not bulk copy out of table 'cont20684C64E88B424BBBBE84921DEDFF77'.
I used the log to get more specific info and I got the following:
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: MyServer-MyMainDatabase-MyMainDatabase2MyTargetDatabase-4
Connecting to Distributor 'MyServer'
Connecting to Publisher 'MyServer.MyMainDatabase'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31

max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[8/3/2005 4:43:30 PM]MyServer.MyMainDatabase: sp_MSgetversion
Initializing the publication 'MyMainDatabase2MyTargetDatabase'
*** [Publication:'MyMainDatabase2MyTargetDatabase'] Publication view generation time: 201 (ms) ***
*** [Publication:'MyMainDatabase2MyTargetDatabase'] Make generation time: 100 (ms) ***
Generating schema script for article '[ContactsCategories]'
Generating conflict schema script for article '[ContactsCategories]'
Generating referential integrity script for article '[ContactsCategories]'
Generating trigger script for article '[ContactsCategories]'
*** [Article:'ContactsCategories'] Time generating all schema scripts: 1762 (ms) ***
Generating schema script for article '[Contacts]'
Generating conflict schema script for article '[Contacts]'
Generating referential integrity script for article '[Contacts]'
Generating trigger script for article '[Contacts]'
*** [Article:'Contacts'] Time generating all schema scripts: 1292 (ms) ***
*** [System table:'MSmerge_contents'] .SCH script generation time: 10 (ms) ***

*** [System table:'MSmerge_tombstone'] .SCH script generation time: 20 (ms) ***

*** [System table:'MSmerge_genhistory'] .SCH script generation time: 21 (ms) ***

*** [System table:'sysmergesubsetfilters'] .SCH script generation time: 30 (ms) ***

[8/3/2005 4:43:34 PM]MyServer.MyMainDatabase: select 1 from [dbo].[ContactsCategories] (TABLOCK HOLDLOCK) where 1=2
[8/3/2005 4:43:34 PM]MyServer.MyMainDatabase: select 1 from [dbo].[Contacts] (TABLOCK HOLDLOCK) where 1=2
Bulk copying snapshot data for system table 'MSmerge_contents'
select * from cont20684C64E88B424BBBBE84921DEDFF77 where 1 = 2
[8/3/2005 4:43:35 PM]MyServer.MyMainDatabase: select * from cont20684C64E88B424BBBBE84921DEDFF77 where 1 = 2
SourceTypeId = 4
SourceName = MyServer
ErrorCode = 0
ErrorText = ODBCBCP/Driver version mismatch
The process could not bulk copy out of table 'cont20684C64E88B424BBBBE84921DEDFF77'.
Disconnecting from Publisher 'MyServer'

I have also found in another forum tha this is related with the files sqlsrv32.dll, sqlsrv32.rll and odbcbcp.dll. The versions of these drivers in my server are:
sqlsrv32.dll: 85.1025
sqlsrv32.rll: 81.9001
odbcbcp.dll: 81.9031
Is it really the problem in the versions of these files? Anyone knows how to update them and if there any risks by doing it?
Thanks in advance...

Try the link below to get started replication is one of the work in progress in SQL Server. Hope this helps.
http://www.replicationanswers.com/Default.asp

Publication doesn't show

To try out replication I have installed several instances of SQL server on a
single computer. With one default server and one named server merge
replication with pull subscription works fine. When I try to add a pull
subscription to an additional named server however, the publication does not
show in the list.
I tried removing the subscription and publication. Then I added the
publication. This makes the publication visible from both named servers when
I use the pull subscription wizard. But when I finish the wizard to add a
pull subscription to any of the servers, this makes the publication not
appear when I try to create a pull subscription to the other server. If I
only delete the subscription (not the publication), the publication does not
show up from any of the named servers.
The publication is configured to allow anonymous subscriptions.
Additionally, I use the same password for the sa account on all servers, so I
think the publication should be accesible to the login used to connect to the
named servers. Any ideas why the publication does not show up in the pull
subscription wizard?
/Daniel
I still don't know what the problem was, but I worked around it by first
creating a push subscription to the server from which I wanted to create a
pull subscription. This, for some reason, made the publication visible in the
pull subscription wizard.

Publication does not exist.

I have an error that states....
DESCRIPTION:Replication-Replication Merge Subsystem: agent R99S-SQLA-
EDI-EDI Merge to 00-r00s-sqla-2 failed. Publication 'EDI Merge to 00'
does not exist.
Due to the fact that there are other consultants setting up/deleteing
replication & do not know how this happened...nonetheless I need to
delete this replication. The publication is not in the tree list in
Local Publications, so I have no way of getting rid of it from there.
I have done some research & I am suppose to look in the
MSmerge_publications table in the distribution dB, but I do not have a
distribution dB.
Any one have a clue about this one?
Larry...
Looks like someone has created a publication from script that has spaces in
the name. You have to delete this publication, and then recreate it
correctly.
You will probably have to edit the system tables to do this.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1185813236.584431.209930@.19g2000hsx.googlegro ups.com...
>I have an error that states....
> DESCRIPTION: Replication-Replication Merge Subsystem: agent R99S-SQLA-
> EDI-EDI Merge to 00-r00s-sqla-2 failed. Publication 'EDI Merge to 00'
> does not exist.
> Due to the fact that there are other consultants setting up/deleteing
> replication & do not know how this happened...nonetheless I need to
> delete this replication. The publication is not in the tree list in
> Local Publications, so I have no way of getting rid of it from there.
>
> I have done some research & I am suppose to look in the
> MSmerge_publications table in the distribution dB, but I do not have a
> distribution dB.
> Any one have a clue about this one?
> Larry...
>

publication database not listed

When I create new subscription there is nothing listed under SQL Server.
I configured Server for replication, then published myDatabase.
Then I wanted to subscribe to this database, but couldn't -
I ckick on Server's Name under tree and tha's it - nothing is shown under it
to pick from.
There is following message in event log:
The replication agent is not registered properly. Rerun SQL Server setup.
We have SQL Server 2000 with spk3 installed.
We have production databases on it and can not rerun installation.
Is there anyway to reconfigure the server or do something else?
Any suggestions will be appreciated.
Thanks.
Can you tell me exactly the steps you take to get this? IE, right click on
the publication, push new subscription, etc.
Then while you are doing this run profiler and ensure you capture all
errors. Then post the results back here.
There have been cases where replication stored procedures go missing. It is
unclear whether these procs where ever installed or if they were deleted
somehow.
Can you run the following in your master database?
select count(*) from sysobjects where type ='p' and report back here with
the count!
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Alan" <Alan@.discussions.microsoft.com> wrote in message
news:823A7863-6166-4164-B02E-F317688CBA9D@.microsoft.com...
> When I create new subscription there is nothing listed under SQL Server.
> I configured Server for replication, then published myDatabase.
> Then I wanted to subscribe to this database, but couldn't -
> I ckick on Server's Name under tree and tha's it - nothing is shown under
it
> to pick from.
> There is following message in event log:
> The replication agent is not registered properly. Rerun SQL Server setup.
> We have SQL Server 2000 with spk3 installed.
> We have production databases on it and can not rerun installation.
> Is there anyway to reconfigure the server or do something else?
> Any suggestions will be appreciated.
> Thanks.

Publication creating bcp files on server

using publication from server one to server two. On server one, I have several directories with bcp files. Can the older files and directories be deleted?

Hi Paul

Are these bcp files being created by merge/tran replication? If so here is a detailed reply from Raymond Mak from a previous post specifically for tran replication. Post back here if you need any further help.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265814&SiteID=1

Cleanup of snapshot files for transactional\snapshot replication is actually handled automatically by the 'distribution cleanup agent' which is basically a SQLServerAgent job that runs the sp_MSdistribution_cleanup stored procedure periodically at the distribution database. Thus, you may want to check the job history of the cleanup agent and see if it had any troubles removing snapshot folders or if it is running at all. And if you find that the distribution cleanup agent had trouble cleaning up the snapshot folders, it is more than likely that either the SQL Server service account or the xp_cmdshell proxy account lacks sufficient privilege to remove the snapshot folders. Now, I suspect that what I have said so far has very little to do with your particular scenario but instead I am guessing that one of your publications has the immediate_sync (select immediate_sync from syspublications at publisher database to confirm) set to 1. Normally, if none of your publications has the immediate_sync property set to 1, the distribution cleanup agent will remove the snapshot folder as soon as the snapshot data has been distributed to all applicable subscribers. However, if any of your publications has the immediate_sync property set to 1, the snapshot files for that publication may stay around until the max distribution retention (default 72 hours) is past. This is because immediate_sync = 1 means that snapshot data should be made available for initializing any new subscriptions added after the snapshot has been generated. The SQL2005 create publication wizard will enable the immediate_sync publication if you check the "Generate snapshot immediately ... " check-box and that may explain how some of your publications have the immediate_sync property set to 1 in the first place.

Hope that helps.

Nabila Lacey