As well as views.

Key words "some cases".

That make a difference between your statement and the one from Carl.

2 Philicart

I cannot understand why you use @Array table in your UDF. I changed it this way:

IF EXISTS (SELECT * FROM sysobjects WHERE name = N'udf_SplitChar')

 DROP FUNCTION udf_SplitChar

GO

CREATE FUNCTION dbo.udf_SplitChar...

Another typical task:

WEB application supplies comma delimited list of IDs.

You need to select rows with IDs mentioned in this list.

Sounds familiar?

IF EXISTS (SELECT * FROM sysobjects WHERE name = N'ListNumericShort')

 DROP...

Are you sure?

Probably my server has only 1GB of RAM but it should not make such a big difference.

Did you join second sysobjects?

2 Carl.

another test for your article.

select O.ID, O.name

from dbo.sysobjects  O, sysobjects O1

GROUP BY O.ID, O.name

-- run time < 1 sec.

select object_id(O.name) as ID_, O.name

from dbo.sysobjects O, sysobjects O1

GROUP...

And in separate table you can trace not only inserted or updated rows, but deleted ones as well.

First of all do not change the schema of traced tables.

Create separate table having columns:

ObjectId, PKValue, UserId, OperationId, TimeRecorded.

Than set up triggers on traced tables to insert references to...

Actually it's a great task:

insert a record without any data in it!

You assign some automatic values but TO WHAT???

If you face such...

2 Datne Garcia

Do you wipe out all records related to deleted instance before creating a new record with the same ID?

Otherwise your historical data about deleted, say, customer will be...

Would it be a great idea to read some headlines on main page before entering forum?

http://www.sqlservercentral.com/columnists/AVigneau/boostyourperformancebadindexdetection.asp

Great stuff. Thanks.

Only 2 notes:

WHERE <...> AND i.indid < 255 and i.name NOT LIKE '_WA_Sys_%'

eliminates NULLs and makes join to sysindexes actually INNER, not LEFT.

I'm not sure...

Great stuff. Thanks.

Only 2 notes:

WHERE <...> AND i.indid < 255 and i.name NOT LIKE '_WA_Sys_%'

eliminates NULLs and makes join to sysindexes actually INNER, not LEFT.

I'm not sure...

Get rid of that procedure.

Look on UPDATES and INSERTs inside of it. It must be lack of WHERE in those statements.

If you need some degug information create dedicated table dbo.tmp_ThisF<..>gSP_debug...

What kind of logic could possibly require to use a cursor in trigger?