Personally, I would go with multiple dbs on a single instance.  I've never used multiple instances on a single machine, but I would imagine there would be a lot of...

Yes.

You just need to qualify the name of the procedure...

exec UtilityDB.dbo.My_Stored_Proc

By the way, sp_help can be run from any database without being qualified because it is stored in the master...

Thats why I said "Depending on how you are getting the value for the day of week"...

Try this...

declare

@date  datetime,

@day_txt varchar(9),

@day_num tinyint

set @date = getdate()

set datefirst 7

select @day_num = datepart(dw, @date)

select @day_txt =

  ...

Depending on how you are getting the value for the day of week, the datefirst function, which sets the first day of the week,  could be affecting it. Take a look at...

Truncating the transaction log will certainly impact it.  You are deleting transactions from the log without backing them up.  It would be like taking a full backup, then tlog backup #1,...

I wonder if you could use @@spid and dbcc input_buffer to get what you need.

Steve

Its important to realize that in SQL Server, there really is no 6th or 7th specific record.  The storage order is completely arbitrary.  Wayne used an "order by" in his query,...

/*

 First, copy your backup file to the new server. 

I will assume that the folder is the same. 

Then you can cut and paste this entire message into...

No problem!  It was driving me nuts, because I knew it was there, but I was looking for sp_makesys......!

Steve

Since I've never dealt with image data, this is just an "uneducated guess", but... what if you DTS'd or otherwise transferred the image data to a new database, then drop...

Try this:

EXEC sp_MS_marksystemobject 'sp_AddMergeArticle'

Steve

Restore the database in which the dts package resides, but restore it to a NEW database using RESTORE ... WITH MOVE.  Don't overwrite your database or the database files!

   RESTORE...

I spoke with my associate and she remembers the issue as well.

She recommends running all of the following:

DBCC UPDATEUSAGE(dbname)

DBCC CHECKDB(dbname)

DBCC CHECKALLOC(dbname)

I would add the DBCC CHECKTABLE(syslogs) as well, for good...

A transaction log backup will perform a truncate after backing up the log.  Therefore, to keep your logs small, and have maximum protection, you should schedule regular transaction log backups...

if @parm1 is null

 begin

 raiserror('null values not allowed, parm1 is null', 16, 1)

 goto xit

 end

-- at the end of the proc....

xit:

return 9

-- or some other number defined to your

-- client...