I did try this, and was able to successfully start it

Start SQL with the /f parameter and traceflag 3608 on.

eg net start mssqlserver /f /T3608

however,

Connect to SQL via the DAC...

FYI, this all began after installing Service Pack 3. While at the end of the installation it said everything was successful and to reboot, after rebooting it hasn't worked...

Download and use the 64-bit one

OP, have you tried my suggestion?

@lokesh - agree, SSIS is ideally the way to go for this type of process

1. Install Office 2007/2012 Data Connectivity Components (http://www.microsoft.com/download/en/confirmation.aspx?id=23734)

2. Change the extension of your excel file to .xlsx

3. Enable "Ad Hoc Distributed Queries" on the server this is running on

4. Run: EXEC master.dbo.sp_MSset_oledb_prop...

#1 you run those on the distributor (they won't work anywhere else anyway)

#2 While I can't say 100%, this is most likely caused by the limitations of you replication setup....

Do not drop and re-add the articles or you will have to go through it all over again! In the replication monitor (or in the SQL agent monitor) navigate...

So now..

Reporting server 1 appears ok but significantly behind on reporting server 2. I need to understand how I can get server 2 catch up.

Reporting server 1 – undistributed transactions...

Need a little more information here...

Is this synching happening as the result of the first time you turned on replication (i.e. the very first sync) or has it been set...

Thanks! That's kinda what I was thinking but wasn't 100% sure on any caveats/gotchas that may arise from doing it

Agree with everyone's replies and wanted to add the obvious tidbit: autofilegrowth introduces a significant amount of contention (as it is a very costly IO activity) and depending on how...

Of course it doesn't work on the Primary Server...It's not supposed to. The OP asked for an automated notification of all log shipped DB's. Log shipping is in...

I created a simple test and never ran into any issues (however this omits the table partition). Can you script out your partition so I can see which how...

Assuming you are using a linked server...in the linked server setup, under server options, did you set the remote procedure calls to true?