ho to do sql replication having sql on diffrent ip addresse

can any body help is sql replication is possibel when we have sql
installed on
servers who have diffrent ip addresses.
here i have three sql servers two servers are are installed at
localley and one is at remote side. my remote side server is having
diffrent ip address when i try to register my remote side server to it
does not registers it gives
connection failed. can any body help me
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Replication-...ict249894.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=865268
If the server is on a non-trusted domain, try creating a client-alias to the
server (client network utility) and then register this servername.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

Hilary...Please provide an example

Please give me more details on what you are saying to do, I'm just not following how I can accomplish this.
Both servers already have this db, the one in the domain is pushing to the db on the DMZ, and now I need to pull 2 tables from this same db from the db on the DMZ.
I am trying to accomplish this with a Anonymous Pull Subscription, but I don't know how to set it up for no sync.
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ekZ$dCQ$FHA.2392@.TK2MSFTNGP09.phx.gbl...
Jude, to make life simple for your self is there anyway you can restore the publishing database to the subscriber and do a no-sync?
This will make life much easier for you.
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
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23%23RCIYP$FHA.264@.tk2msftngp13.phx.gbl...
How can I setup an anonymous pull subscription, using the sp_ scripts for the pull subscription & pull agent, for NO SYNC?
Jude
Can you contact me offline. I have a bit of a write up on how to do this.
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
"JLS" <judes@.email.uophx.edu> wrote in message news:exbkymo$FHA.356@.TK2MSFTNGP12.phx.gbl...
Please give me more details on what you are saying to do, I'm just not following how I can accomplish this.
Both servers already have this db, the one in the domain is pushing to the db on the DMZ, and now I need to pull 2 tables from this same db from the db on the DMZ.
I am trying to accomplish this with a Anonymous Pull Subscription, but I don't know how to set it up for no sync.
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ekZ$dCQ$FHA.2392@.TK2MSFTNGP09.phx.gbl...
Jude, to make life simple for your self is there anyway you can restore the publishing database to the subscriber and do a no-sync?
This will make life much easier for you.
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
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23%23RCIYP$FHA.264@.tk2msftngp13.phx.gbl...
How can I setup an anonymous pull subscription, using the sp_ scripts for the pull subscription & pull agent, for NO SYNC?
Jude
|||Yes, absolutely, how do I contact you offline?
If it's easier, you can contact me at your convenience, toll free 1-800-sartomer, extension 4154 or have the operator page Judy Shoop or directly to my office is 610.363.4154.
Thanx!
Jude
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:eMLs6Zp$FHA.3096@.TK2MSFTNGP14.phx.gbl...
Can you contact me offline. I have a bit of a write up on how to do this.
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
"JLS" <judes@.email.uophx.edu> wrote in message news:exbkymo$FHA.356@.TK2MSFTNGP12.phx.gbl...
Please give me more details on what you are saying to do, I'm just not following how I can accomplish this.
Both servers already have this db, the one in the domain is pushing to the db on the DMZ, and now I need to pull 2 tables from this same db from the db on the DMZ.
I am trying to accomplish this with a Anonymous Pull Subscription, but I don't know how to set it up for no sync.
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ekZ$dCQ$FHA.2392@.TK2MSFTNGP09.phx.gbl...
Jude, to make life simple for your self is there anyway you can restore the publishing database to the subscriber and do a no-sync?
This will make life much easier for you.
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
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23%23RCIYP$FHA.264@.tk2msftngp13.phx.gbl...
How can I setup an anonymous pull subscription, using the sp_ scripts for the pull subscription & pull agent, for NO SYNC?
Jude
|||Use my email address - but here is the doc I put together.
The requirement is that DATABASE be replicated bi-directionally internally
and externally. There are several options to do this, bi-directional
transactional replication was chosen as it does not modify the schema. Merge
replication, and updateable subscribers all modify the schema with the
addition of a GUID column.
To get around the firewall problem the internal database will replicate to
the external database, and the external database changes will be pulled
internally. The internal server will be configured as an anonymous
subscriber of the external server's publication as a named subscriber will
not work.
Steps required configure replication.
1) connect to the production database, right click on each of the
production tables and set the identity attribute to be not for replication.
Configure the increment to be 2. You will need to modify the following
tables.
TableName1WithIdentityColumn
TableName2WithIdentityColumn
TableName3WithIdentityColumn
TableName4WithIdentityColumn
The best/only way to configure these tables is to right click on them in
Enterprise Manager and set the identity property accordingly. Figure 1 is a
correctly configured table.
2) After all of the tables have been configured, back up the database,
and restore it on the subscriber. Ensure that no users are accessing the
database at this time.
3) Once the database has been restored create the publication on the
Publisher and the Subscriber. Use the attached script for this, editing for
the correct server and database names. - this script is a publication where
the name conflicts section is keep existing table intact, and its a nosync
subscription.
4) Once you have done this you need to run the same script in your
external server. Make sure you have configured your subscriber using its
NetBIOS name in Client Network Utility. A Fully Qualified Domain Name will
not work; it must be a NetBIOS name. Please refer to Figure 2 for an
example.
5) Once you have configured replication, deploy the replication stored
procedures on both sides. Please refer to the attached script to do this.
(this script was generated by running sp_scriptpublicationcustomprocs
6) Once the replication stored procedures are in place you have to
reset the identity seed on both sides. We will assign even numbers to the
internal server, and external numbers to the external server.
7) To do this issue the following commands. Note that TableName5 is the
only table which has to be fixed, and the fix is illustrated in red:
dbcc checkident('TableName5')
--Checking identity information: current identity value '8854', current
column value '8854'.
--DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
--ok as the number is even
dbcc checkident('TableName5')
--Checking identity information: current identity value '448', current
column value '448'.
--DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
--ok as the number is even
dbcc checkident('TableName6)
--Checking identity information: current identity value '19', current column
value '19'.
--DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
--not ok as the number is odd
--incrementing it up to the nearest even number
dbcc checkident('TableName7', reseed,20)
--Checking identity information: current identity value '19', current column
value '20'.
--DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
--now correct
dbcc checkident('TableName8')
--Checking identity information: current identity value '32', current column
value '32'.
--DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
--ok as the number is even
8) Repeat for the Subscriber (external server). This time all the
identity values should be reseeded to the next highest odd number.
9) Schedule the distribution agents to start every 5 minutes - this
will guarantee an restart in the event of failure.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:eCOXKey$FHA.1408@.TK2MSFTNGP15.phx.gbl...
Yes, absolutely, how do I contact you offline?
If it's easier, you can contact me at your convenience, toll free
1-800-sartomer, extension 4154 or have the operator page Judy Shoop or
directly to my office is 610.363.4154.
Thanx!
Jude
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eMLs6Zp$FHA.3096@.TK2MSFTNGP14.phx.gbl...
Can you contact me offline. I have a bit of a write up on how to do this.
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
"JLS" <judes@.email.uophx.edu> wrote in message
news:exbkymo$FHA.356@.TK2MSFTNGP12.phx.gbl...
Please give me more details on what you are saying to do, I'm just not
following how I can accomplish this.
Both servers already have this db, the one in the domain is pushing to
the db on the DMZ, and now I need to pull 2 tables from this same db from
the db on the DMZ.
I am trying to accomplish this with a Anonymous Pull Subscription, but I
don't know how to set it up for no sync.
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ekZ$dCQ$FHA.2392@.TK2MSFTNGP09.phx.gbl...
Jude, to make life simple for your self is there anyway you can
restore the publishing database to the subscriber and do a no-sync?
This will make life much easier for you.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%23%23RCIYP$FHA.264@.tk2msftngp13.phx.gbl...
How can I setup an anonymous pull subscription, using the sp_
scripts for the pull subscription & pull agent, for NO SYNC?
Jude

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,Have you applied the post-SP3a hotfix?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fix
- are you referring to SP4?
"Tom Moreau" wrote:
> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becoming
> a bit of a pain for our poor network guys. The other odd thing is that the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:
> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,Have you applied the post-SP3a hotfix?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fi
x
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from o
ne
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to th
e
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becomi
ng
> a bit of a pain for our poor network guys. The other odd thing is that th
e
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cu
ll
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,
Have you applied the post-SP3a hotfix?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
..
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,
|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becoming
> a bit of a pain for our poor network guys. The other odd thing is that the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>
|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
..
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

High CPU utilization

Could anyone help me in finding out why the cpu utilization is very high?

I have two servers say, Server A , server B. There is a transactional replication going on from server A to B

There is a table say Table A on server A, which is being replicated to server B.

I created a trigger insert and update trigger on Table A on server B (i.e. on subscriber). Since then, the CPU utilization for server B is very high 80-90%

when i used profiler, i could see .whenever replication stored proc for insert or update executes..cpu utilization goes up..

trigger just insert the updated/inserted rows into some other table.

Could anyone tell me why the cpu utilization has gone up so much? i am using sql server 2005

thanx

If you see spiked CPU usage after adding the trigger, then it's obvious the trigger is the problem. Trigger does add overhead, how much depends on what the trigger does. Also, what was CPU utilization before trigger, 0%? 50%? Are you doing any queries inside the trigger? If so you may want to look at the plans to see if your queries are optimized, in profiler you should also be able to look at reads, writes, cpu, duration for each statement as well.

High CPU utilization

Could anyone help me in finding out why the cpu utilization is very
high?
I have two servers say, Server A , server B. There is a transactional
replication going on from server A to B
There is a table say Table A on server A, which is being replicated to
server B.
I created a trigger insert and update trigger on Table A on server B
(i.e. on subscriber). Since then, the CPU utilization for server B is
very high 80-90%
when i used profiler, i could see .whenever replication stored proc for
insert or update executes..cpu utilization goes up..
trigger just insert the updated/inserted rows into some other table.
Could anyone tell me why the cpu utilization has gone up so much? Does
Creating trigger on the subscriber cause performance problem? i am
using sql server 2005
thanx
Vishal
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much? Does
> Creating trigger on the subscriber cause performance problem? i am
> using sql server 2005
Yes it is
http://www.sql-server-performance.co...r_counters.asp
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegro ups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high?
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much? Does
> Creating trigger on the subscriber cause performance problem? i am
> using sql server 2005
> thanx
>
|||What is this trigger doing? Frequently when you want a trigger fired as part
of a replication process you should place the triggering action in a
different table. So if you want the trigger fired when you have DML against
table a, and the trigger writes to table b, you get better performance by
creating a separate article which writes to table b, and encapsulate the
trigger logic in the stored procedure.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegro ups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high?
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much? Does
> Creating trigger on the subscriber cause performance problem? i am
> using sql server 2005
> thanx
>
|||Thank you for your reply.
Let me explain you lil further. What i have is a server A and Server B.
On server A I have a database say dbA which is being replicated to
server B using transactional replication. In dbA, i have a table say
table A which is being replicated to server B (ReplTableA) .
Now I am interested in tracking the changes occring to the records of
table A. So whenever there is an insert in table A, I want to insert
that record in history table. Whenever there is an update in table A, I
want to insert that updated record in the history table. So for this i
am using a trigger. but instead of creating a trigger on table A on dbA
(on server A), I am creating a trigger on the replicated
table(ReplTableA) on server B (I thoght this will improve the
performance on server A) . So whenever replication procedure (for
insert & update for ReplTableA) executes, the trigger fires.
Beacause of this cpu utilization of server B has gone up so much (80-90
%)
So is it good thing to write a trigger on the ReplTableA or should i
write a trigger on the original table Table A on server A?
Or is there any thing i can do to reduce the CPU utilization? Could you
please elaborate on creating a seperate artical and encapsulating the
trigger logic in a stored proc ?
Thanks
--Vishal
Hilary Cotter wrote:[vbcol=seagreen]
> What is this trigger doing? Frequently when you want a trigger fired as part
> of a replication process you should place the triggering action in a
> different table. So if you want the trigger fired when you have DML against
> table a, and the trigger writes to table b, you get better performance by
> creating a separate article which writes to table b, and encapsulate the
> trigger logic in the stored procedure.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "Vishal" <rvishal1305@.gmail.com> wrote in message
> news:1161069980.591285.61830@.b28g2000cwb.googlegro ups.com...
|||On 17 Oct 2006 10:12:13 -0700, "Vishal" <rvishal1305@.gmail.com> wrote:
>So is it good thing to write a trigger on the ReplTableA or should i
>write a trigger on the original table Table A on server A?
Should be OK on serverB.

>Or is there any thing i can do to reduce the CPU utilization? Could you
>please elaborate on creating a seperate artical and encapsulating the
>trigger logic in a stored proc ?
Aha, he seems to be suggesting using a redundant replication article
instead of a trigger. Elegant idea!
But really, the trigger should work, too.
Can you post the SQL for the trigger and the DDL for the table and
indexes? Odds are it's just a missing index or something along those
lines.
J.
[vbcol=seagreen]
>Thanks
>--Vishal
>
>Hilary Cotter wrote:

High CPU utilization

The CPU utilization on one of the servers is always around 50%, sometimes
it went to 100%, I turned on Profiler, did not find T-SQL statement using
long CPU time. Also check sp_who2 and find msdb is the most CPU user, the cumulated CPU time is 2742463. There were no other jobs running, just sqlserver agent-alert, which is default How to find the top cpu users? Thanks
Hi,
Can you check the taskmanager and confirm SQLSERVR.EXE is using more CPU? IF
SQL Server then
analyze the each connections connected to server using sp_who, sp_who2 and
dbcc inputbuffer commands.
You can try stopping the SQLSERVERAGENT service as well.
Thanks
Hari
MCDBA
"lhse" <lhse@.discussions.microsoft.com> wrote in message
news:A8BBBC49-4647-4206-B515-B4904E7553A2@.microsoft.com...
> The CPU utilization on one of the servers is always around 50%, sometimes
> it went to 100%, I turned on Profiler, did not find T-SQL statement using
> long CPU time. Also check sp_who2 and find msdb is the most CPU user, the
cumulated CPU time is 2742463. There were no other jobs running, just
sqlserver agent-alert, which is default How to find the top cpu users?
Thanks
>
|||You can run profiler and sort by cpu.. You can also insert the profiler data
into a SQL table and start doing select group by user, app, etc to find the
largest CPU user..
Remember that other maintenance type things go on, like checkpoint, lazy
writer, etc which can use CPU as well.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"lhse" <lhse@.discussions.microsoft.com> wrote in message
news:A8BBBC49-4647-4206-B515-B4904E7553A2@.microsoft.com...
> The CPU utilization on one of the servers is always around 50%, sometimes
> it went to 100%, I turned on Profiler, did not find T-SQL statement using
> long CPU time. Also check sp_who2 and find msdb is the most CPU user, the
cumulated CPU time is 2742463. There were no other jobs running, just
sqlserver agent-alert, which is default How to find the top cpu users?
Thanks
>

High CPU utilization

The CPU utilization on one of the servers is always around 50%, sometimes
it went to 100%, I turned on Profiler, did not find T-SQL statement using
long CPU time. Also check sp_who2 and find msdb is the most CPU user, the cu
mulated CPU time is 2742463. There were no other jobs running, just sqlserve
r agent-alert, which is default How to find the top cpu users? ThanksHi,
Can you check the taskmanager and confirm SQLSERVR.EXE is using more CPU? IF
SQL Server then
analyze the each connections connected to server using sp_who, sp_who2 and
dbcc inputbuffer commands.
You can try stopping the SQLSERVERAGENT service as well.
Thanks
Hari
MCDBA
"lhse" <lhse@.discussions.microsoft.com> wrote in message
news:A8BBBC49-4647-4206-B515-B4904E7553A2@.microsoft.com...
> The CPU utilization on one of the servers is always around 50%, sometimes
> it went to 100%, I turned on Profiler, did not find T-SQL statement using
> long CPU time. Also check sp_who2 and find msdb is the most CPU user, the
cumulated CPU time is 2742463. There were no other jobs running, just
sqlserver agent-alert, which is default How to find the top cpu users?
Thanks
>|||You can run profiler and sort by cpu.. You can also insert the profiler data
into a SQL table and start doing select group by user, app, etc to find the
largest CPU user..
Remember that other maintenance type things go on, like checkpoint, lazy
writer, etc which can use CPU as well.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"lhse" <lhse@.discussions.microsoft.com> wrote in message
news:A8BBBC49-4647-4206-B515-B4904E7553A2@.microsoft.com...
> The CPU utilization on one of the servers is always around 50%, sometimes
> it went to 100%, I turned on Profiler, did not find T-SQL statement using
> long CPU time. Also check sp_who2 and find msdb is the most CPU user, the
cumulated CPU time is 2742463. There were no other jobs running, just
sqlserver agent-alert, which is default How to find the top cpu users?
Thanks
>

High CPU utilization

Could anyone help me in finding out why the cpu utilization is very
high'
I have two servers say, Server A , server B. There is a transactional
replication going on from server A to B
There is a table say Table A on server A, which is being replicated to
server B.
I created a trigger insert and update trigger on Table A on server B
(i.e. on subscriber). Since then, the CPU utilization for server B is
very high 80-90%
when i used profiler, i could see .whenever replication stored proc for
insert or update executes..cpu utilization goes up..
trigger just insert the updated/inserted rows into some other table.
Could anyone tell me why the cpu utilization has gone up so much' Does
Creating trigger on the subscriber cause performance problem' i am
using sql server 2005
thanxVishal
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
Yes it is
http://www.sql-server-performance.c...or_counters.asp
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high'
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
> thanx
>|||What is this trigger doing? Frequently when you want a trigger fired as part
of a replication process you should place the triggering action in a
different table. So if you want the trigger fired when you have DML against
table a, and the trigger writes to table b, you get better performance by
creating a separate article which writes to table b, and encapsulate the
trigger logic in the stored procedure.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high'
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
> thanx
>|||Thank you for your reply.
Let me explain you lil further. What i have is a server A and Server B.
On server A I have a database say dbA which is being replicated to
server B using transactional replication. In dbA, i have a table say
table A which is being replicated to server B (ReplTableA) .
Now I am interested in tracking the changes occring to the records of
table A. So whenever there is an insert in table A, I want to insert
that record in history table. Whenever there is an update in table A, I
want to insert that updated record in the history table. So for this i
am using a trigger. but instead of creating a trigger on table A on dbA
(on server A), I am creating a trigger on the replicated
table(ReplTableA) on server B (I thoght this will improve the
performance on server A) . So whenever replication procedure (for
insert & update for ReplTableA) executes, the trigger fires.
Beacause of this cpu utilization of server B has gone up so much (80-90
%)
So is it good thing to write a trigger on the ReplTableA or should i
write a trigger on the original table Table A on server A?
Or is there any thing i can do to reduce the CPU utilization? Could you
please elaborate on creating a seperate artical and encapsulating the
trigger logic in a stored proc ?
Thanks
--Vishal
Hilary Cotter wrote:[vbcol=seagreen]
> What is this trigger doing? Frequently when you want a trigger fired as pa
rt
> of a replication process you should place the triggering action in a
> different table. So if you want the trigger fired when you have DML agains
t
> table a, and the trigger writes to table b, you get better performance by
> creating a separate article which writes to table b, and encapsulate the
> trigger logic in the stored procedure.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "Vishal" <rvishal1305@.gmail.com> wrote in message
> news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...|||On 17 Oct 2006 10:12:13 -0700, "Vishal" <rvishal1305@.gmail.com> wrote:
>So is it good thing to write a trigger on the ReplTableA or should i
>write a trigger on the original table Table A on server A?
Should be OK on serverB.

>Or is there any thing i can do to reduce the CPU utilization? Could you
>please elaborate on creating a seperate artical and encapsulating the
>trigger logic in a stored proc ?
Aha, he seems to be suggesting using a redundant replication article
instead of a trigger. Elegant idea!
But really, the trigger should work, too.
Can you post the SQL for the trigger and the DDL for the table and
indexes? Odds are it's just a missing index or something along those
lines.
J.
[vbcol=seagreen]
>Thanks
>--Vishal
>
>Hilary Cotter wrote:

High CPU utilization

Could anyone help me in finding out why the cpu utilization is very
high'
I have two servers say, Server A , server B. There is a transactional
replication going on from server A to B
There is a table say Table A on server A, which is being replicated to
server B.
I created a trigger insert and update trigger on Table A on server B
(i.e. on subscriber). Since then, the CPU utilization for server B is
very high 80-90%
when i used profiler, i could see .whenever replication stored proc for
insert or update executes..cpu utilization goes up..
trigger just insert the updated/inserted rows into some other table.
Could anyone tell me why the cpu utilization has gone up so much' Does
Creating trigger on the subscriber cause performance problem' i am
using sql server 2005
thanxVishal
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
Yes it is
http://www.sql-server-performance.com/performance_monitor_counters.asp
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high'
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
> thanx
>|||What is this trigger doing? Frequently when you want a trigger fired as part
of a replication process you should place the triggering action in a
different table. So if you want the trigger fired when you have DML against
table a, and the trigger writes to table b, you get better performance by
creating a separate article which writes to table b, and encapsulate the
trigger logic in the stored procedure.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Vishal" <rvishal1305@.gmail.com> wrote in message
news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
> Could anyone help me in finding out why the cpu utilization is very
> high'
> I have two servers say, Server A , server B. There is a transactional
> replication going on from server A to B
> There is a table say Table A on server A, which is being replicated to
> server B.
> I created a trigger insert and update trigger on Table A on server B
> (i.e. on subscriber). Since then, the CPU utilization for server B is
> very high 80-90%
> when i used profiler, i could see .whenever replication stored proc for
> insert or update executes..cpu utilization goes up..
> trigger just insert the updated/inserted rows into some other table.
> Could anyone tell me why the cpu utilization has gone up so much' Does
> Creating trigger on the subscriber cause performance problem' i am
> using sql server 2005
> thanx
>|||Thank you for your reply.
Let me explain you lil further. What i have is a server A and Server B.
On server A I have a database say dbA which is being replicated to
server B using transactional replication. In dbA, i have a table say
table A which is being replicated to server B (ReplTableA) .
Now I am interested in tracking the changes occring to the records of
table A. So whenever there is an insert in table A, I want to insert
that record in history table. Whenever there is an update in table A, I
want to insert that updated record in the history table. So for this i
am using a trigger. but instead of creating a trigger on table A on dbA
(on server A), I am creating a trigger on the replicated
table(ReplTableA) on server B (I thoght this will improve the
performance on server A) . So whenever replication procedure (for
insert & update for ReplTableA) executes, the trigger fires.
Beacause of this cpu utilization of server B has gone up so much (80-90
%)
So is it good thing to write a trigger on the ReplTableA or should i
write a trigger on the original table Table A on server A?
Or is there any thing i can do to reduce the CPU utilization? Could you
please elaborate on creating a seperate artical and encapsulating the
trigger logic in a stored proc ?
Thanks
--Vishal
Hilary Cotter wrote:
> What is this trigger doing? Frequently when you want a trigger fired as part
> of a replication process you should place the triggering action in a
> different table. So if you want the trigger fired when you have DML against
> table a, and the trigger writes to table b, you get better performance by
> creating a separate article which writes to table b, and encapsulate the
> trigger logic in the stored procedure.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "Vishal" <rvishal1305@.gmail.com> wrote in message
> news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
> > Could anyone help me in finding out why the cpu utilization is very
> > high'
> >
> > I have two servers say, Server A , server B. There is a transactional
> > replication going on from server A to B
> >
> > There is a table say Table A on server A, which is being replicated to
> > server B.
> >
> > I created a trigger insert and update trigger on Table A on server B
> > (i.e. on subscriber). Since then, the CPU utilization for server B is
> > very high 80-90%
> >
> > when i used profiler, i could see .whenever replication stored proc for
> > insert or update executes..cpu utilization goes up..
> >
> > trigger just insert the updated/inserted rows into some other table.
> >
> > Could anyone tell me why the cpu utilization has gone up so much' Does
> > Creating trigger on the subscriber cause performance problem' i am
> > using sql server 2005
> >
> > thanx
> >|||On 17 Oct 2006 10:12:13 -0700, "Vishal" <rvishal1305@.gmail.com> wrote:
>So is it good thing to write a trigger on the ReplTableA or should i
>write a trigger on the original table Table A on server A?
Should be OK on serverB.
>Or is there any thing i can do to reduce the CPU utilization? Could you
>please elaborate on creating a seperate artical and encapsulating the
>trigger logic in a stored proc ?
Aha, he seems to be suggesting using a redundant replication article
instead of a trigger. Elegant idea!
But really, the trigger should work, too.
Can you post the SQL for the trigger and the DDL for the table and
indexes? Odds are it's just a missing index or something along those
lines.
J.
>Thanks
>--Vishal
>
>Hilary Cotter wrote:
>> What is this trigger doing? Frequently when you want a trigger fired as part
>> of a replication process you should place the triggering action in a
>> different table. So if you want the trigger fired when you have DML against
>> table a, and the trigger writes to table b, you get better performance by
>> creating a separate article which writes to table b, and encapsulate the
>> trigger logic in the stored procedure.
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>> 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
>>
>> "Vishal" <rvishal1305@.gmail.com> wrote in message
>> news:1161069980.591285.61830@.b28g2000cwb.googlegroups.com...
>> > Could anyone help me in finding out why the cpu utilization is very
>> > high'
>> >
>> > I have two servers say, Server A , server B. There is a transactional
>> > replication going on from server A to B
>> >
>> > There is a table say Table A on server A, which is being replicated to
>> > server B.
>> >
>> > I created a trigger insert and update trigger on Table A on server B
>> > (i.e. on subscriber). Since then, the CPU utilization for server B is
>> > very high 80-90%
>> >
>> > when i used profiler, i could see .whenever replication stored proc for
>> > insert or update executes..cpu utilization goes up..
>> >
>> > trigger just insert the updated/inserted rows into some other table.
>> >
>> > Could anyone tell me why the cpu utilization has gone up so much' Does
>> > Creating trigger on the subscriber cause performance problem' i am
>> > using sql server 2005
>> >
>> > thanx
>> >

High CPU Usage

Hello,
I need your help urgently.
I have a MsSQL server database that behaves normally all day, but at certain
times the server's cpu usage rises abnormally.
There's no increase in the amount of transactions sent to the server,
there's no scheduled job running, and apparently there's no other
application running on the server.
Could you tell me the tools availble to identify what's the cause of the
high CPU usage? with Perfomance monitor I get the %Processor Time but I
don't get the source of the problem.
Any ideas,
TIA
Eduardo Sicouret
You can go into task manager and select the "Processes" tab. Once there
click the CPU column to sort it... this should show you which
process/application is using the CPU the most.
HTH
Adam J Warne, MCDBA
"Eduardo Sicouret" wrote:

> Hello,
> I need your help urgently.
> I have a MsSQL server database that behaves normally all day, but at certain
> times the server's cpu usage rises abnormally.
> There's no increase in the amount of transactions sent to the server,
> there's no scheduled job running, and apparently there's no other
> application running on the server.
> Could you tell me the tools availble to identify what's the cause of the
> high CPU usage? with Perfomance monitor I get the %Processor Time but I
> don't get the source of the problem.
> Any ideas,
> TIA
> Eduardo Sicouret
>
>
|||I get that SQL server is the process that's taking the most CPU time... but
I don't know what is it doing
Eduardo
"Adam Warne" <AdamWarne@.discussions.microsoft.com> escribi en el mensaje
news:AE07D8AD-7AAA-40F0-86B2-0CBA02854D42@.microsoft.com...[vbcol=seagreen]
> You can go into task manager and select the "Processes" tab. Once there
> click the CPU column to sort it... this should show you which
> process/application is using the CPU the most.
> HTH
> --
> Adam J Warne, MCDBA
>
> "Eduardo Sicouret" wrote:
|||My apologies Eduardo, I misread the question ... one of those days.
In this instance, you could run a trace through SQL profiler to see what
transactions are running when the CPU usage peaks.
Alternatively, you can execute "sp_who2" and this will show you the spids
that have a high CPU time. You can then run "dbcc inputbuffer (spid)" to see
what command is being executed for that spid.
Adam J Warne, MCDBA
"Eduardo Sicouret" wrote:

> I get that SQL server is the process that's taking the most CPU time... but
> I don't know what is it doing
> Eduardo
> "Adam Warne" <AdamWarne@.discussions.microsoft.com> escribió en el mensaje
> news:AE07D8AD-7AAA-40F0-86B2-0CBA02854D42@.microsoft.com...
>
>

High CPU time per user as soon as they connect?

On a couple of our servers, users are currently scoring very
high on "CPU Time" as reported by Enterprise Manager and by
sp_who2, both as soon as they log in, and afterwards -
5,000,000 at login and 47,000,000 later on are the top figures.
Most of the fleet is on SQL Server 2000 Service Pack 2, with
between 2 and 8 hard-working processors. The hardest working
server is on Service Pack 3(a), clustered, and its top 5
current values in CPU time are between 382,847 and 705,879.
The servers are all on clients' sites and networks, with client's
choice of firewall. Usual application is a Java interface using
jTDS, but CPU time is also reported high for a new Query Analyzer
connection. SQL Server, not Windows, accounts are most often used.
Clients aren't complaining of poor performance, apparently, but
maybe they already gave up phoning for that.
So, should we worry? Reboot? Reindex? Patch? Disinfect?
Or ask around, "Who left SQL Profiler running"...i would run profiler to find out whats going on.
i would also run perfmon to find out what average cpu is
over the entire day
otherwise, you have nothing from which to make reasonable
assessments
>--Original Message--
>On a couple of our servers, users are currently scoring
very
>high on "CPU Time" as reported by Enterprise Manager and
by
>sp_who2, both as soon as they log in, and afterwards -
>5,000,000 at login and 47,000,000 later on are the top
figures.
>Most of the fleet is on SQL Server 2000 Service Pack 2,
with
>between 2 and 8 hard-working processors. The hardest
working
>server is on Service Pack 3(a), clustered, and its top 5
>current values in CPU time are between 382,847 and
705,879.
>The servers are all on clients' sites and networks, with
client's
>choice of firewall. Usual application is a Java
interface using
>jTDS, but CPU time is also reported high for a new Query
Analyzer
>connection. SQL Server, not Windows, accounts are most
often used.
>Clients aren't complaining of poor performance,
apparently, but
>maybe they already gave up phoning for that.
>So, should we worry? Reboot? Reindex? Patch?
Disinfect?
>Or ask around, "Who left SQL Profiler running"...
>.
>

High Availibility SQL 2000

Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersj=F6Replication copies data elements, not the entire database. Foreign keys,
stored procedures, unique constraints, and user-defined functions are not
transferred in replication.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<alstersjo@.hotmail.com> wrote in message
news:1183648932.226829.223710@.m36g2000hse.googlegroups.com...
Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersjö|||On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Replication copies data elements, not the entire database. Foreign keys,
> stored procedures, unique constraints, and user-defined functions are not
> transferred in replication.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> <alster...@.hotmail.com> wrote in message
> news:1183648932.226829.223710@.m36g2000hse.googlegroups.com...
> Hi
> We are setting up a soloution with 2 sql 2000 servers as a manuel
> failover soloution.
> My question is: What is best, to use transactional replication or log
> shipping?
> My old book about sql2000 says only logshipping for this situation but
> i cant't figure out why not to use replication.
> And please, I'ts not my desission to use this layout I only follow
> orders so its not possible to use SQL clustering or SQL2005 for
> example.
> Best Regards Henrik Alstersj=F6
Just eo ensure I'm on the right page, when you state that you are
utilizing a manual failover, does that mean you will not be utilizing
Microsoft Clustering Services (MSCS)? Using this would take care of
any necessity for log shipping or replication and you could simply
utilize an active/passive configuration.
Otherwise, if you aren't utilizing this, what would the damage be of
simply backing up your database and when a manual failover is
necessary, simply restore the backup to your secondary server? Of
course, this may be a bit time consuming, however, with your current
situation, it doesn't sound like high availability is a top priority
and the time to restore your database should be fairly quick.
Aaron|||On 5 Juli, 22:06, acorcoran <acorco...@.gmail.com> wrote:
> On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>
>
> > Replication copies data elements, not the entire database. Foreign key=s,
> > stored procedures, unique constraints, and user-defined functions are n=ot
> > transferred in replication.
> > --
> > Geoff N. Hiten
> > Senior Database Administrator
> > Microsoft SQL Server MVP
> > <alster...@.hotmail.com> wrote in message
> >news:1183648932.226829.223710@.m36g2000hse.googlegroups.com...
> > Hi
> > We are setting up a soloutionwith 2 sql 2000servers as a manuel
> > failover soloution.
> > My question is: What is best, to use transactional replication or log
> > shipping?
> > My old book about sql2000 says only logshipping for this situation but
> > i cant't figure out why not to use replication.
> > And please, I'ts not my desission to use this layout I only follow
> > orders so its not possible to use SQL clustering or SQL2005 for
> > example.
> > Best Regards Henrik Alstersj=F6
> Just eo ensure I'm on the right page, when you state that you are
> utilizing a manual failover, does that mean you will not be utilizing
> Microsoft Clustering Services (MSCS)? Using this would take care of
> any necessity for log shipping or replication and you could simply
> utilize an active/passive configuration.
> Otherwise, if you aren't utilizing this, what would the damage be of
> simply backing up your database and when a manual failover is
> necessary, simply restore the backup to your secondary server? Of
> course, this may be a bit time consuming, however, with your current
> situation, it doesn't sound like high availability is a top priority
> and the time to restore your database should be fairly quick.
> Aaron- D=F6lj citerad text -
> - Visa citerad text -
Hi
Thanks for your input, both of you.
The reason that we don't want to use backup restore functionality is
that the failovertime is not needed to bee quick but the data must be
up to date to the crash. So if we have a sevear servercrash we cant
get so fresh data from the sql server.
Regards Henrik

High Availibility SQL 2000

Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersj=F6Replication copies data elements, not the entire database. Foreign keys,
stored procedures, unique constraints, and user-defined functions are not
transferred in replication.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<alstersjo@.hotmail.com> wrote in message
news:1183648932.226829.223710@.m36g2000hse.googlegroups.com...
Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersj|||On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Replication copies data elements, not the entire database. Foreign keys,
> stored procedures, unique constraints, and user-defined functions are not
> transferred in replication.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> <alster...@.hotmail.com> wrote in message
> news:1183648932.226829.223710@.m36g2000hse.googlegroups.com...
> Hi
> We are setting up a soloution with 2 sql 2000 servers as a manuel
> failover soloution.
> My question is: What is best, to use transactional replication or log
> shipping?
> My old book about sql2000 says only logshipping for this situation but
> i cant't figure out why not to use replication.
> And please, I'ts not my desission to use this layout I only follow
> orders so its not possible to use SQL clustering or SQL2005 for
> example.
> Best Regards Henrik Alstersj=F6
Just eo ensure I'm on the right page, when you state that you are
utilizing a manual failover, does that mean you will not be utilizing
Microsoft Clustering Services (MSCS)? Using this would take care of
any necessity for log shipping or replication and you could simply
utilize an active/passive configuration.
Otherwise, if you aren't utilizing this, what would the damage be of
simply backing up your database and when a manual failover is
necessary, simply restore the backup to your secondary server? Of
course, this may be a bit time consuming, however, with your current
situation, it doesn't sound like high availability is a top priority
and the time to restore your database should be fairly quick.
Aaron|||On 5 Juli, 22:06, acorcoran <acorco...@.gmail.com> wrote:
> On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>
>
>
s,[vbcol=seagreen]
ot[vbcol=seagreen]
>
>
>
>
> Just eo ensure I'm on the right page, when you state that you are
> utilizing a manual failover, does that mean you will not be utilizing
> Microsoft Clustering Services (MSCS)? Using this would take care of
> any necessity for log shipping or replication and you could simply
> utilize an active/passive configuration.
> Otherwise, if you aren't utilizing this, what would the damage be of
> simply backing up your database and when a manual failover is
> necessary, simply restore the backup to your secondary server? Of
> course, this may be a bit time consuming, however, with your current
> situation, it doesn't sound like high availability is a top priority
> and the time to restore your database should be fairly quick.
> Aaron- D=F6lj citerad text -
> - Visa citerad text -
Hi
Thanks for your input, both of you.
The reason that we don't want to use backup restore functionality is
that the failovertime is not needed to bee quick but the data must be
up to date to the crash. So if we have a sevear servercrash we cant
get so fresh data from the sql server.
Regards Henrik

High Availibility SQL 2000

Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersj
Replication copies data elements, not the entire database. Foreign keys,
stored procedures, unique constraints, and user-defined functions are not
transferred in replication.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<alstersjo@.hotmail.com> wrote in message
news:1183648932.226829.223710@.m36g2000hse.googlegr oups.com...
Hi
We are setting up a soloution with 2 sql 2000 servers as a manuel
failover soloution.
My question is: What is best, to use transactional replication or log
shipping?
My old book about sql2000 says only logshipping for this situation but
i cant't figure out why not to use replication.
And please, I'ts not my desission to use this layout I only follow
orders so its not possible to use SQL clustering or SQL2005 for
example.
Best Regards Henrik Alstersj
|||On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Replication copies data elements, not the entire database. Foreign keys,
> stored procedures, unique constraints, and user-defined functions are not
> transferred in replication.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> <alster...@.hotmail.com> wrote in message
> news:1183648932.226829.223710@.m36g2000hse.googlegr oups.com...
> Hi
> We are setting up a soloution with 2 sql 2000 servers as a manuel
> failover soloution.
> My question is: What is best, to use transactional replication or log
> shipping?
> My old book about sql2000 says only logshipping for this situation but
> i cant't figure out why not to use replication.
> And please, I'ts not my desission to use this layout I only follow
> orders so its not possible to use SQL clustering or SQL2005 for
> example.
> Best Regards Henrik Alstersj
Just eo ensure I'm on the right page, when you state that you are
utilizing a manual failover, does that mean you will not be utilizing
Microsoft Clustering Services (MSCS)? Using this would take care of
any necessity for log shipping or replication and you could simply
utilize an active/passive configuration.
Otherwise, if you aren't utilizing this, what would the damage be of
simply backing up your database and when a manual failover is
necessary, simply restore the backup to your secondary server? Of
course, this may be a bit time consuming, however, with your current
situation, it doesn't sound like high availability is a top priority
and the time to restore your database should be fairly quick.
Aaron
|||On 5 Juli, 22:06, acorcoran <acorco...@.gmail.com> wrote:
> On Jul 5, 11:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>
>
>
>
>
> Just eo ensure I'm on the right page, when you state that you are
> utilizing a manual failover, does that mean you will not be utilizing
> Microsoft Clustering Services (MSCS)? Using this would take care of
> any necessity for log shipping or replication and you could simply
> utilize an active/passive configuration.
> Otherwise, if you aren't utilizing this, what would the damage be of
> simply backing up your database and when a manual failover is
> necessary, simply restore the backup to your secondary server? Of
> course, this may be a bit time consuming, however, with your current
> situation, it doesn't sound like high availability is a top priority
> and the time to restore your database should be fairly quick.
> Aaron- Dlj citerad text -
> - Visa citerad text -
Hi
Thanks for your input, both of you.
The reason that we don't want to use backup restore functionality is
that the failovertime is not needed to bee quick but the data must be
up to date to the crash. So if we have a sevear servercrash we cant
get so fresh data from the sql server.
Regards Henrik

High availability at subscribers using database mirroring

I have a mirrored database with transactional replication publishing
to 2 databases on different servers.
The amount of data written to the principal is fairly low.
The requirement is that at least one of the subscribers must be
available at all times with a latency of no greater than five minutes.
I thus have redundancy at the publisher via mirroring and at the
subscribers via multiple databases containing the same data, but I
can't see how to achieve redundancy at the distributor, since the
distribution database cannot be mirrored.
What is the recommended method of making the distributor highly
available? At this site there is reluctance to pursue SQL clustering
and to rename servers as described in BOL. At the moment it looks like
a need a set of scripts to completely set up replication from scratch
if the machine where the distributor DB lives goes offline.
Or, will Katmai offer new features to make all of the replication
components as highly available as the publisher can now be via
mirroring?
Hi Garry,
I understand that you would like to implement a high availability SQL
Server replication. You implemented Database mirroring for your principal
server and multiple databases with same data at the subscribers, but you
would like to know how to implement redundancy at the distributor since the
distribution database cannot be mirrored.
If I have misunderstood, please let me know.
I recommend that you can create a failover cluster for your distributer.
Deploy the distribution database to the virtual server instance. Also, for
your scenario, I think that it is better to use failover cluster for your
publisher since it just need two servers, but to implement a high
availability database mirroring, it needs three servers, principal server,
witness server and mirror server.
For how to setup a SQL Server 2005 failover cluster, you may refer to:
How to: Create a New SQL Server 2005 Failover Cluster (Setup)
http://msdn2.microsoft.com/en-us/library/ms179530.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

High %privileged and interrupt time

Had a high CPU on my SQL Servers and on further investigation, it appears
that the % privileged and interrupt time were high and not user time.
What should I account for such behavior especially if it occurs on many SQL
servers at the same time ?
Cannot find anything odd in the event or SQL Logs.Hi
"Hassan" wrote:

> Had a high CPU on my SQL Servers and on further investigation, it appears
> that the % privileged and interrupt time were high and not user time.
> What should I account for such behavior especially if it occurs on many SQ
L
> servers at the same time ?
> Cannot find anything odd in the event or SQL Logs.
You can also look at interupts/sec. If you are getting excessive number of
interupts it may be a disc issue so also look at Physical Disk counters.
John

High %privileged and interrupt time

Had a high CPU on my SQL Servers and on further investigation, it appears
that the % privileged and interrupt time were high and not user time.
What should I account for such behavior especially if it occurs on many SQL
servers at the same time ?
Cannot find anything odd in the event or SQL Logs.
Hi
"Hassan" wrote:

> Had a high CPU on my SQL Servers and on further investigation, it appears
> that the % privileged and interrupt time were high and not user time.
> What should I account for such behavior especially if it occurs on many SQL
> servers at the same time ?
> Cannot find anything odd in the event or SQL Logs.
You can also look at interupts/sec. If you are getting excessive number of
interupts it may be a disc issue so also look at Physical Disk counters.
John

Hiding data in replicated tables

Hello,
I have a merge replication setup between two sql 2000 servers. It works
fine, but there is some data in one table
that I wish to hide - at the subscriber database.
This data is in 4 columns in one table. It would be best if I could exclude
the table altogether from the replication process
but this cannot be done because the table is referenced by a foreign key
constraint with another table required in the replication process.
Also I cannot vertically filter out the columns because the columns are not
nullable. I did try selecting out the data by using the 'where' clause
and trying to eliminate the data that I wish to hide from the result set,
however this did not work.
Am not sure how I can go about hiding this data because it should not be
seen at the subscriber.
Any help will be appreciated.
Thanks,
Marise
How about hiding the data by using a view on the subscriber?
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Dear Paul,
I am not too sure what you mean by hiding data using a view on the
subscriber...please explain some more how this can be done.
Because this is data hiding at the database level. i.e. anyone who logs
into the database and runs a select query should not be able to see these
four columns in this one table.
Thanks,
Marise
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:u4Xlhg$dFHA.3712@.TK2MSFTNGP12.phx.gbl...
> How about hiding the data by using a view on the subscriber?
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Nothing special here - as long as they don't have select rights on the
table, the only way they'll be able to get to see any data is through the
view.
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks for the response. The replicated database sits away from our location
and the user name that we use to do replication has been assigned to us - we
do not have the capability to alter database permissions. I wanted to find a
way to restrict the data itself being copied over at all.
Please let me know if there is a way.
Thanks,
Marise
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:u2kqR4AfFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Nothing special here - as long as they don't have select rights on the
> table, the only way they'll be able to get to see any data is through the
> view.
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>