I've long-since audited them, and there are no jobs that do this--directly. There might be hidden processes secreted away under unknown myriad layers of code; this is unlikely, but...

As it's your first week, I wouldn't focus too much on security issues or (more important) playing the blame game--there's going to be too much about the work environment that...

Worked like a charm. Hmm. Testing here... looks like I get courier, no fonts, bold, or italics. If so, that makes it a tricky call...

Performing a standard SQL Server database backup (on master or anything else) will not detach databases.

Going along with what everyone's been saying, barring some very unlikely code implementations you may...

Dang, how 'bout that. I'd guess it does this for ALL databases. I'll have to stick a "KilroyWasHere" table in model and see if it shows up after the next restore...

(1) What noeld said. We had a system like this and it worked well, but we could get away with updating it once a day. If they need up to...

To add to what SQLBill says, it's been my experience that--all else being equal--restores take longer than backups, ranging maybe from 10% to 25% longer. (Hard drive space has to...

The "guest" user account is (by default and by necessity) enabled in the master database, and (again by immutable default) is granted membership in the public role... and that role...

You'll have two SQL Server instances (call them A and B). Each SQL Instance will contain an instance of database ASPSTATE... and those database are differentiated by the SQL Server...

Never heard of this happening before myself. Some top-of-the-head ideas:

 - Check the database autoclose setting

 - Check the SQL logs (in EM, under Management / SQL Server Logs). Was the service...

Sounds good. If and when I get a machine to test it on, I'll do so before "going live".

   Philip

Nope, I just used sp_attach_db. Less typing, same effect.

(Also, if you look at the source code, they seem functionally identical, in that they...

I hit a similar situation once. SQL Server was stopped, I manually deleted the (single) .ldf file, and when I started up SQL Server again the file was marked "suspect"...

A few quick ideas, not too fleshed out:

Some user (or scheduled) submitted routine is causing this to happen. SQL Server does not arbitrarily choose to bloat tempdb. Use of temp...

A model that should work in these cases is that of  type-subtype.  A key component is that there is a set of properties shared by all the items you are...