"The identity range managed by replication is
full and must be updated by a replication agent."
my merge replication agent is constantly running and syncing.
why isn't it re-seeding the values in the ident. cols ?
You have blown your range on the subscriber. You need to select a range
which will not be blown between syncs. This is rather difficult to recover
from. Check out this article for more info.
http://www.simple-talk.com/sql/database-administration/the-identity-crisis-in-replication/
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
"Tony B." <Test@.spam.ca> wrote in message
news:u8XhNLnDHHA.3520@.TK2MSFTNGP04.phx.gbl...
> "The identity range managed by replication is
> full and must be updated by a replication agent."
> my merge replication agent is constantly running and syncing.
> why isn't it re-seeding the values in the ident. cols ?
>
Showing posts with label constantly. Show all posts
Showing posts with label constantly. Show all posts
Wednesday, March 28, 2012
Friday, February 24, 2012
Memory Paging
I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?
The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?
The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
Memory Paging
I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have t
o
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have t
o
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
Memory Paging
I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
--
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
--
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
Subscribe to:
Posts (Atom)