That's a bit, well, insane... why is the trigger there in the first place if you're going to just disable it?  Either the trigger is bad or your code is...

IF you're going to use an undocumented sproc, why not go all the way and get ALL the filenames at once?

 CREATE TABLE #Directory (RowNum INT IDENTITY(1,1),FileName SYSNAME,Depth...

Unless they are set based procs... "Death by SQL"... the idea of code reuse to process single records will absolutely kill performance and make more maintanence nightmares than you can...

SET TRANSACTION ISOLATION LEVEL SERIALIZABLE

First question would be... Why aren't you using an IDENTITY column to do this along with Scope_Identity.

Next question would be... Please post your SP...

Nicely done, Adrian...

The big advantage of creating file groups on different disks is purely physical... you get more read write heads involved.  Of course, the same could be said for partitioning one...

You could also make a batch job that runs a "SELECT" via OSQL to create a CSV file as the output.... Windows Task Scheduler takes care of the rest...

Great suggestion.  Old gaming trick... if you can't move, "change color".

Ditto on the nulls...

CREATE PROCEDURE [dbo].[SEQVAL] @tblname varchar(100) AS

Begin tran

UPDATE CASE_NUM_SEQ SET CURRVALUE = CURRVALUE + INCR WHERE SEQ_CD = @tblname

SELECT CURRVALUE FROM CASE_NUM_SEQ WHERE SEQ_CD = @tblname

commit

We had a similar procedure at work (created by a 3rd...

Heh... "for reference only"... just wait until they ask "how many logins this week"... and they will...

Anyway, thanks for the feedback, Charlie.

Cross post

Cross post

You've certainly got CROSS-POSTING down pat!

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=361685

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=169&messageid=361683

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=169&messageid=361682

Download one of the lite versions of SQL or MSDE... they're free...