Limitayion of indexes

Hello there
I've been heard that after amount of data on table (Approx 1,000,000 records
and more) according to the type of index, the index performance is become
mutch more slower.
Does someone knows what is the limitation and how can i handle of it?Roy,shalom
It depends on how often your table is acceseed (insert/update/deleted) .
What is a WHERE condion and how often is changed. I'd prefer to rebuild
indexes on all my user tables one a w.
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:%23Cxk3h$SGHA.6084@.TK2MSFTNGP14.phx.gbl...
> Hello there
> I've been heard that after amount of data on table (Approx 1,000,000
> records and more) according to the type of index, the index performance is
> become mutch more slower.
> Does someone knows what is the limitation and how can i handle of it?
>|||Whell Uri
Have you ever worked with approx 10,000,000 records?
and i know that there is fill factor for this case.
Do you have any idea for what is use?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23HcZEl$SGHA.5828@.TK2MSFTNGP14.phx.gbl...
> Roy,shalom
> It depends on how often your table is acceseed (insert/update/deleted) .
> What is a WHERE condion and how often is changed. I'd prefer to rebuild
> indexes on all my user tables one a w.
>
> "Roy Goldhammer" <roy@.hotmail.com> wrote in message
> news:%23Cxk3h$SGHA.6084@.TK2MSFTNGP14.phx.gbl...
>|||Roy
> Have you ever worked with approx 10,000,000 records?
:-))) Yes , even much much more

> and i know that there is fill factor for this case.
Yes , FillFactor is created along with a creation of index on the table

> Do you have any idea for what is use?
Do you want to know what FILLFACTOR to put on the table?
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:O%23Rwtu$SGHA.5736@.TK2MSFTNGP10.phx.gbl...
> Whell Uri
> Have you ever worked with approx 10,000,000 records?
> and i know that there is fill factor for this case.
> Do you have any idea for what is use?
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23HcZEl$SGHA.5828@.TK2MSFTNGP14.phx.gbl...
>|||Index fragmentation can increase the amount of I/O required to scan an
index, and this would be more likely and noticable on large tables. DBCC
SHOWCONTIG will reveal the amount of fragmentation and DBCC DBREINDEX or
DBCC INDEXDEFRAG can be occasionally run the correct the problem, which
typically accumulates over time.
Understanding SQL Server's DBCC SHOWCONTIG:
http://www.sql-server-performance.c..._showcontig.asp
Microsoft SQL Server 2000 Index Defragmentation Best Practices:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:%23Cxk3h$SGHA.6084@.TK2MSFTNGP14.phx.gbl...
> Hello there
> I've been heard that after amount of data on table (Approx 1,000,000
> records and more) according to the type of index, the index performance is
> become mutch more slower.
> Does someone knows what is the limitation and how can i handle of it?
>