You can use the following script to remove the extra data file:

USE InsLogicQuest

GO

DBCC SHRINKFILE ('InsLogicQuest_DataEm03',EMPTYFILE)

GO

ALTER DATABASE InsLogicQuest

REMOVE FILE InsLogicQuest_DataEm03

GO

This will move all of the data to the InsLogicQuest_Data data file...

I think Gail has provided the correct answer. I have seen this happen when anti-virus software is scanning the data files. You can stop the anti-virus service, restart the SQL...

You will also need to remove all subscriptions first. Per BOL:

An article cannot be removed if one or more subscriptions to it exist. This stored procedure (sp_droparticle) is executed at...

We use LiteSpeed to backup a 2TB db to local disk in about 2.5 hours. We do weekly full and daily diff since the db is in Simple recovery mode....

JumpstartTV.com has some SSIS examples under:

Channels > Technology > Database > SQL Server > SQL Server 2005

Right-click on the SQL Server Agent in Enterprise Manager, select the "Job System" tab, and increase the value for "Maximum job history rows per job".

I believe the default is 100....

I believe this is the article you are referring to: http://support.microsoft.com/kb/949095

Looks like it will be released sometime next month.

WOW.... Thanks Matt. Guess I need to go back to the coffee machine. I tried to make this way too difficult.

The Blackberry/Smartphone debate came up at the company I work for. It was decided to use Blackberry because it uses a push technology where a smartphone uses a pull technology....

You could remove all the users except you from the database so no one but you can access it.

I have used Lightspeed for years and it works great, however it's fairly pricy. I have heard from Quest reps that a row level restore is possible with the enterprise...

Our security folks use Tripwire for auditing like this.

We run SQL servers on ESX as well and they work great for small to medium applications. You license one ESX server with SQL Enterprise and all your small/medium db's...

The tempdb gets rebuilt each time the SQL Server Service is restarted in both 2000 and 2005. I would not recommend shinking the tempdb as it may have to auto-grow...

In the Transform Data Task under options, you can set "Insert batch size" to keep your transaction log from growing out of control on large inserts.