You need to use a lock hint to prevent access see BOL "Locking Hints". Also # temp tables are only visible to the connection that created it. Thsu connection 1...

Seems sound, does the path it barks about exist? I believe it tests for the validity and that is why you get the error.

"Don't roll your eyes at me. I...

Yeah, and whatever works just as long as it works.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Try sp_detach_db to detach both and then sp_attach_db where you can set the path of both files when reattaching to the server.

"Don't roll your eyes at me. I will tape...

You can setup fielgroups and specifiy which filegroups you want a nonclustered index in and which the table is in. We generally only do this on large databases to try...

Have you checked the SQL Server Logs and Event Viewer to see if any details?

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Must be. But I try that and still have no issues. I will test some more tomorrow to see if I can get it to happen. May be something the...

Take a look at this, may apply in your case where you have the db and log backedup in the same file. You did say you had 2 files visible...

I generally only worry with the patches if they apply to me directly. You have to be carefull thought with patches outside the SP method as they have a shorter...

I believe this is the correct syntax.

Delete Openquery(db2, 'select * from mytable')

If not then look at http://search.support.microsoft.com/search/default.aspx?Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&Product=sql&Query=openquery%2520delete&Queryc=openquery+delete&withinResults=false&srchstep=0&KeywordType=ALL&Titles=false&numDays=&maxResults=25 and see if anything helps answer the question.

"Don't roll your eyes at me....

Cannot join these 2 INSERTS into 1. Have to run seperately. Unless you try a union query with the values to table1.

SELECT 'jack','mary','billy'

UNION ALL

select * from Table1 where city='charlotte'

but this...

I am stumped, what is the exact message you are getting (verbaitum) as I find no answer at this point unless there is some major version difference from the original...

When I do the schedule option it adds an item to Management->SQLAgents->jobs named like so DBNAME backup which I deleted to stop this schedule otherwise you did not actually...

Try the service pack but I do believe it is the difference in processors as you don't have as many thread pools servicing requests. Microsoft use the number of processors...

Actually have a friend who owns one and yes it is awkward at first and takes a bit getting used to. However is much better than the first generation was...