Automatic Range Management - I give up

I have searched through this NG as well as searched BOL concerning this
process called Automatic Range Management, which is suggested as an easy way
to handle reseeding of the identity values. But I have no idea how to set up
ARM. I looked through the properties of my publications and subscriptions
and couldn't find anything for ARM. Nor do the wizards reveal any setting
for ARM.
So, howya do it?
Roger,
in the publication properties, on the articles tab, click on the elipsis
button which gives access to the article properties. There is a tab for
identities, and a checkbox at the top for automatic range management.
Assuming you haven't yet subscribed, it won't be greyed out and you can then
set the size of the range etc.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||THANK YOU!!!!!!
"Paul Ibison" wrote:

> Roger,
> in the publication properties, on the articles tab, click on the elipsis
> button which gives access to the article properties. There is a tab for
> identities, and a checkbox at the top for automatic range management.
> Assuming you haven't yet subscribed, it won't be greyed out and you can then
> set the size of the range etc.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Auto update statistics and Auto create statistics Options

According to BOL, Adding statistics improves query
performance because the SQL Server query optimizer can
better determine how to evaluate a query.
However, someone says that statistics updates will cause
locks on tables at unpredictable times and impact
performance for users.
Should we turn the options on ?
If we turn them off, how can we update the statistics ?
Can it be done in the Database Maintenance Plan ?Technically, yes... it's theoretically possible for auto update statistics
to cause performance degradation under certain performance situations. But
generally speaking... the potential performance problems associated with
turning the option off... are MUCH larger than the potential problems of
leaving them on...
I normally keep them on for databases that I help to manage for customers.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:a8cd01c3eb89$eb171030$a601280a@.phx.gbl...
> According to BOL, Adding statistics improves query
> performance because the SQL Server query optimizer can
> better determine how to evaluate a query.
> However, someone says that statistics updates will cause
> locks on tables at unpredictable times and impact
> performance for users.
> Should we turn the options on ?
> If we turn them off, how can we update the statistics ?
> Can it be done in the Database Maintenance Plan ?

Auto update statistics and Auto create statistics Options

According to BOL, Adding statistics improves query
performance because the SQL Server query optimizer can
better determine how to evaluate a query.
However, someone says that statistics updates will cause
locks on tables at unpredictable times and impact
performance for users.
Should we turn the options on ?
If we turn them off, how can we update the statistics ?
Can it be done in the Database Maintenance Plan ?Technically, yes... it's theoretically possible for auto update statistics
to cause performance degradation under certain performance situations. But
generally speaking... the potential performance problems associated with
turning the option off... are MUCH larger than the potential problems of
leaving them on...
I normally keep them on for databases that I help to manage for customers.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:a8cd01c3eb89$eb171030$a601280a@.phx.gbl...

quote:

---

> According to BOL, Adding statistics improves query
> performance because the SQL Server query optimizer can
> better determine how to evaluate a query.
> However, someone says that statistics updates will cause
> locks on tables at unpredictable times and impact
> performance for users.
> Should we turn the options on ?
> If we turn them off, how can we update the statistics ?
> Can it be done in the Database Maintenance Plan ?

---