I must be on a slow day... what's the irony here??

Check out sp_attach_db.

Splits '1,2,3,4' to

1

2

3

4

where the comma is the delimiter in this case. I won't go into the mechanics of the code but at least you'll know what it's for. ...

Can we have more details about those anomalies??? I can confirm that this looks like a "bug" but I'd like to know more about those known problems

HTH.

Hmm, try runing the profiler to see what the wizard is doing... you should be able to trace the problem from there.

Do you have a package with a nameless step??

This will get you going :

CREATE TABLE dbo.Test (id int not null primary key clustered)

GO

CREATE TRIGGER dbo.tr_test_IUD ON dbo.Test

FOR INSERT, UPDATE, DELETE

AS

SET NOCOUNT ON

ROLLBACK TRANSACTION

RAISERROR ('This is just a...

Also check if there is a unique index that ignores duplicates.

Are you sure about all that... AFAIK, constraint are also indexed and used in queries.

Back to the begining, how many rows do you get when you do the select only?

Maybe you could speed this up if you added an indexed calculated field on the long ip (the ones you calculate on the fly)... maybe that could give you some...

Please do not cross-post, we monitor all boards.

Finish the thread here : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=225047

Just a taught... maybe it would be faster to run the clustered index seek if the startIP and endIP columns were at the start of the index instead of a...

This is the proc that does the job :

CREATE PROCEDURE dbo.SearchColumns @Items as varchar(8000), @ItemsCount as smallint --avoid calling split twice

AS

SET NOCOUNT ON

SELECT

O.id

, O.Name

FROM dbo.SysObjects O

WHERE Exists (

SELECT 1

FROM...