Hi Perry

Thanks for replying

We don't actually have an issue with networks or connectivity.

The situation I'm describing is where something catastrophic has happened in our WAN infrastructure. Our primary data center...

Just to let you know that the truncation worked and subsequent checkdb came back clean:-).

However when I check the suspect_pages table in msdb, I still see the corrupt page...

Thanks.

I have requested a restore of the db to another server. We have known issues with our storage subsystem which are making life "interesting" and have been restoring up...

We got sorted on this one - old faithful did the trick - REBOOT

To prove the concept, we rebooted the passive node, ran the service pack from the active node...

Hey,

Just wondering was there ever a resolution to this issue?

I am experiencing the same

Paul

On the secondary server, logshipping installs a copy job and a restore job.

You can set the copy job to run as often as you like. If you are worried...

the extra two slashes should be OK. Windows will just ignore them.

Is there nothing in the SQL Error Log?

If you can't get at it through EM try browsing to \MSSQL\DATA\MSSQL\LOG

Sometimes it's something as simple as MSDTC not being started before SQL...

You need to check which OS account your SQL Server Service runs as. More than likely it can't authenticate to either the source or the destination.

A "net use" may well...

Try checking SQL Server Network Utility on your Win2003 server to ensure that Named Pipes is enabled and configured correctly

Hi,

Oracle appear to recommend a product called "Connect for ODBC" by Data Direct Technologies.

http://www.datadirect.com/products/odbc/odbcunix/index.ssp

I have just downloaded and installed this product on our Solaris Server although I...

Found a solution in another forum:

DECLARE @TableName NVARCHAR(100)

DECLARE @SQLString NVARCHAR(500)

DECLARE @ParmDefinition NVARCHAR(500)

DECLARE @dbsize int

DECLARE @dbname VARCHAR(30)

SET @dbname = 'Northwind'

SET @TableName = @dbname + N'.dbo.sysfiles'

SET @ParmDefinition = N'@dbsize int out'

SET...

Found a solution in another forum:

DECLARE @TableName NVARCHAR(100)

DECLARE @SQLString NVARCHAR(500)

DECLARE @ParmDefinition NVARCHAR(500)

DECLARE @dbsize int

DECLARE @dbname VARCHAR(30)

SET @dbname = 'Northwind'

SET @TableName = @dbname + N'.dbo.sysfiles'

SET @ParmDefinition = N'@dbsize int out'

SET...