I'd use Frank's suggestion as it is operation based and not conversion based (much faster on large sets).

check this link from sybase's site

they use top 7 just like in sql server... maybe you can search more on their site :

http://search.sybase.com/kbx/changerequests?bug_id=340736

I've just read the books online and you need pretty high rights to execute this command (db_owner or db_ddladmin), contrary to what Steve suggested.

Maybe you can write a stored proc...

You just answered it yourself, if you need to rewrite the whole application to allow for a design change that is not needed... and not approved by anyone here. ...

what script did you use?

Now you seem to be comparing oranges with tangerines. Getting closer but it's still 2 different things. I'm currently working with a denormalized DB and it's a big...

Yes the user will be able to do this permanently as long as he has inserts rights on the table.

Obviously you need to grant access to all tables where the...

I've already worked with a similar table design... but for weekdays (sunday to saturday). The table kept the days we visited a client for a given week. I...

Can't wait to see it too.. and Yoda's as well :-).

While it is true that too many indexes can cripple database performances (with many inserts and updates on the table), properly created indexes (like for foreign keys and there matching...

I tested my code before posting it and it worked as my results show. I never said that the query wasn't possible to create, I was simply stating...

btw I don't think Noeld' solution would work... try this :

CREATE TABLE [Test] (

[PKtest] [int] IDENTITY (1, 1) NOT NULL ,

[Col1] [int] NOT NULL ,

[Col2] [int] NOT NULL ,

CONSTRAINT...

wouldn't it be better to simply erase the duplicate rows and adding a unique constraint so that the data is well maintained?

Is "procperiod" the primary key of the table? or actually

Is "pk_taxdata" the index that covers the column "procperiod"?

I doubt you can force the plan to use an irrelevant index.

BTW...

What do you mean by that?? Are you inserting small chunks of a really large transaction to avoid dead locks? Are you simply trying to reduce round trips...