Showing posts with label progress. Show all posts
Showing posts with label progress. Show all posts

Wednesday, March 28, 2012

Index size problem

I am copying our progress database over to our Sql Server 2000 system.
I found a problem with the index size being too large. The description
is 2000 bytes and Sql Server is giving me an error saying I have
exceeded the index size of 900 bytes.
Is there a way around this?
Thanks,
Tom.
i assume you're trying to index a description column that's a
varchar(2000). if so, don't index it. there's probably no good reason to
index that column.
Thomas Scheiderich wrote:

> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.
|||No. At least not without changing the data type to less than 901 bytes.
Gert-Jan
Thomas Scheiderich wrote:
> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.
(Please reply only to the newsgroup)

Index size problem

I am copying our progress database over to our Sql Server 2000 system.
I found a problem with the index size being too large. The description
is 2000 bytes and Sql Server is giving me an error saying I have
exceeded the index size of 900 bytes.
Is there a way around this?
Thanks,
Tom.i assume you're trying to index a description column that's a
varchar(2000). if so, don't index it. there's probably no good reason to
index that column.
Thomas Scheiderich wrote:

> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.|||No. At least not without changing the data type to less than 901 bytes.
Gert-Jan
Thomas Scheiderich wrote:
> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.
(Please reply only to the newsgroup)

Index size problem

I am copying our progress database over to our Sql Server 2000 system.
I found a problem with the index size being too large. The description
is 2000 bytes and Sql Server is giving me an error saying I have
exceeded the index size of 900 bytes.
Is there a way around this?
Thanks,
Tom.i assume you're trying to index a description column that's a
varchar(2000). if so, don't index it. there's probably no good reason to
index that column.
Thomas Scheiderich wrote:
> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.|||No. At least not without changing the data type to less than 901 bytes.
Gert-Jan
Thomas Scheiderich wrote:
> I am copying our progress database over to our Sql Server 2000 system.
> I found a problem with the index size being too large. The description
> is 2000 bytes and Sql Server is giving me an error saying I have
> exceeded the index size of 900 bytes.
> Is there a way around this?
> Thanks,
> Tom.
--
(Please reply only to the newsgroup)

Monday, March 12, 2012

Index is not faster any more

After I have modified couple columns my database access is very slow in that table. (Update Statistics Rx_Control is in Progress). It happened before I got back to same status by restoring the data. I really don't want to restore this time. Please some one post a sloution.

Thank you
Raj SankarOriginally posted by raj_sankar
After I have modified couple columns my database access is very slow in that table. (Update Statistics Rx_Control is in Progress). It happened before I got back to same status by restoring the data. I really don't want to restore this time. Please some one post a sloution.

Thank you
Raj Sankar
Are these updates on any index columns. Try rebuilding the index using
DBCC dbreindex

Joe|||Originally posted by mkg_1232000
Are these updates on any index columns. Try rebuilding the index using
DBCC dbreindex

Joe

The index is ok, Some how execution plan changed. Now every this ok after uodating the statistics. how ever the foloowing problem remains.

from query analyser.
select * from table_name where store = '3' --is faster and using index scan.

Declare @.store as int
set @.store = '3'
select * from table_name where store = @.store --is very slow and using table scan.

I don't how to fix this, it was ok before.