Hi Gail,

Is the script I posted from Ola's site? I wasn't trying to take credit for anyone's script, it's just something I use.

Andrew

Sorry! Just realised that the firewall won't be the problem.

Try connecting again and have a look at the SQL Server error logs and the application/system event logs.

Alright this is starting to bug me now.

Can you have a look at the Windows Firewall settings on the server running SQL?

No worries, good link

http://blog.sqlauthority.com/2010/03/17/sql-server-difference-between-rollback-immediate-and-with-no_wait-during-alter-database/

Summary

No Wait - will cause the statement you are executing to fail if there are open transactions

Roll back Immediate - will rollback open transactions when you execute...

In the SQL Server Configuration Manager, is TCP/IP and Names Pipes enabled for remote connections?

If they have recently be changed the instance will also need to be restarted.

What you're looking for is objects that no longer exist in the database but may be generating the allocation errors

Same error when connecting in SSMS?

OK, just trying to help.

As the first allocation error does not reference an object try creating a maintenance plan with a rebuild index task in it. Script out the index...

If you can connect to the instance from the client side with SSMS then the problem must be with stunnel.

Sorry I'm not familiar with stunnel.

Hi,

Was the database in single user mode when you ran the repair?

Andrew

I know this one doesn't cover everything but it's free!

http://www.amazon.co.uk/Introducing-Microsoft%C2%AE-Server%C2%AE-2012-ebook/dp/B007PJ6DSW/ref=sr_1_1?ie=UTF8&qid=1359487225&sr=8-1

OK, as you can connect to the instance within the network the problem is not there.

Have you tried specifying the port in the connection to the instance?

Hi,

Have a look at Brent Ozar's website, loads of good scripts there (sp_Blitz).

http://www.brentozar.com/

Andrew

Hi, I use the following script, is this any help?

CREATE PROCEDURE dbo.[IndexRebuild] AS

DECLARE @TableName NVARCHAR(500);

DECLARE @SQLIndex NVARCHAR(max);

DECLARE @RowCount INT;

DECLARE @Counter INT;

DECLARE @IndexAnalysis TABLE

(AnalysisID INT IDENTITY(1,1) NOT NULL PRIMARY KEY,

TableName...

Are you using a SQL Server authenticated account to login?