Writing good SQL requires a totally different mindset than writing good procedural code.  Set oriented thinking isn't a natural mode for COBOL programmers.  Many moons ago, I made that shift...

Check the permissions for the account under which SQL Server runs.  It's that account which will need permissions to create the database files.  You should also check the sql agent...

In EM, could you check to make sure the server is set for mixed mode authentication?

You could hack the sytem tables but I'd advise against it.  The following will generate the stored proc calls to change everything not owner by DBO to DBO, no strenuous...

I don't think you can do it during a restore operation but you can use dbcc shrinkfile after the restore to reduce the log size.

The sound of this makes me a little uneasy.  If your developers are doing troubleshooting on the replicate, might they not want to change physical structures and alter objects and...

I can't see any advantage this form of access would have over a cursor.  Cursors are slower than set operations, but I'd bet this is one case where the cursor...

create table #mileage (mileage int NOT NULL)

go

insert #milage (mileage) values (3000)

insert #milage (mileage) values (6000)

insert #milage (mileage) values (9000)

insert #milage (mileage) values (12000)

.

.

.

INSERT INTO ##tblTmpMaintSched

SELECT b.Mileage, a.Task from tblMaintSched a,...

Ok, so much for guessing....

Could you post the query execution plan?  That should point out the rough spot or spots.

Is there an index on tbl_value?

If there's no index, and it's doing a table scan, the cache is probably being re-used for pages that don't fit the criteria, so it...

Hi.

Just a guess at an answer based on the subject.

From Books Online:

Permissions

DBCC INPUTBUFFER permissions default to members of the sysadmin fixed server role only, who can see any SPID....

I think your problem may be that the database you detatched from the old server has the old collation carried along with it when you attach it.  In older releases,...

If you don't need all the rows from the lookup tables returned, whether you find a match or not, you shouldn't be using OUTER joins. 

Here's a clip from Books...

Yes, you need the joins to do the lookups, but do they have to be OUTER joins?  Outer joins may return more data than you need and hamper the optimizer's...

Do you really need all those outer joins?  You're doing a lot more than just looking up matching values with this.