Can't get mirroring working for all DBs?

I'm getting the following errors when trying to set up mirroring for a DB.
[PRINCIPAL]
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid99
Message
Communications to the remote server instance 'TCP://SQL2:5022' failed before
database mirroring was fully started. The ALTER DATABASE command failed.
Retry the command when the remote database is started.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid99
Message
Error: 1413, Severity: 16, State: 1.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid37s
Message
The mirroring connection to "TCP://SQL2:5022" has timed out for database
"DB1" after 10 seconds without a response. Check the service and network
connections.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid37s
Message
Error: 1479, Severity: 16, State: 1.
[MIRROR]
Date 3/2/2007 2:52:49 PM
Log SQL Server (Current - 3/5/2007 8:46:00 AM)
Source spid35s
Message
The mirroring connection to "TCP://SQL1:5022" has timed out for database
"DB1" after 5 seconds without a response. Check the service and network
connections.
Date 3/2/2007 2:52:49 PM
Log SQL Server (Current - 3/5/2007 8:46:00 AM)
Source spid35s
Message
Error: 1479, Severity: 16, State: 1.
This only occurs for this particular DB. I have mirroring running
successfully for 4 other DBs. The only difference I can see is that the
problematic DB is significantly larger than the other mirrored DBs... it's
~70GB.
I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
instances.
Please help...interesting. cant say I've seen this before but trying running consistancy
check DBCC CHECKDB (refer to BOL) perhaps a corruption in the db is causing
the timeout.
M.
"slin" <slin@.discussions.microsoft.com> wrote in message
news:E52523C6-0B5C-4507-B6FA-9439EFD1C02E@.microsoft.com...
> I'm getting the following errors when trying to set up mirroring for a DB.
> [PRINCIPAL]
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid99
> Message
> Communications to the remote server instance 'TCP://SQL2:5022' failed
> before
> database mirroring was fully started. The ALTER DATABASE command failed.
> Retry the command when the remote database is started.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid99
> Message
> Error: 1413, Severity: 16, State: 1.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid37s
> Message
> The mirroring connection to "TCP://SQL2:5022" has timed out for database
> "DB1" after 10 seconds without a response. Check the service and network
> connections.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid37s
> Message
> Error: 1479, Severity: 16, State: 1.
>
> [MIRROR]
> Date 3/2/2007 2:52:49 PM
> Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> Source spid35s
> Message
> The mirroring connection to "TCP://SQL1:5022" has timed out for database
> "DB1" after 5 seconds without a response. Check the service and network
> connections.
>
> Date 3/2/2007 2:52:49 PM
> Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> Source spid35s
> Message
> Error: 1479, Severity: 16, State: 1.
>
> This only occurs for this particular DB. I have mirroring running
> successfully for 4 other DBs. The only difference I can see is that the
> problematic DB is significantly larger than the other mirrored DBs... it's
> ~70GB.
> I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
> instances.
> Please help...|||Already did a DBCC CHECKDB... No errors. I'm using Profiler to see if it'll
show me what's failing, but not having any luck so far...
-S
"Mark Broadbent" wrote:
> interesting. cant say I've seen this before but trying running consistancy
> check DBCC CHECKDB (refer to BOL) perhaps a corruption in the db is causing
> the timeout.
> M.
>
> "slin" <slin@.discussions.microsoft.com> wrote in message
> news:E52523C6-0B5C-4507-B6FA-9439EFD1C02E@.microsoft.com...
> > I'm getting the following errors when trying to set up mirroring for a DB.
> >
> > [PRINCIPAL]
> >
> > Date 3/2/2007 2:52:06 PM
> > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > Source spid99
> > Message
> > Communications to the remote server instance 'TCP://SQL2:5022' failed
> > before
> > database mirroring was fully started. The ALTER DATABASE command failed.
> > Retry the command when the remote database is started.
> >
> > Date 3/2/2007 2:52:06 PM
> > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > Source spid99
> > Message
> > Error: 1413, Severity: 16, State: 1.
> >
> > Date 3/2/2007 2:52:06 PM
> > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > Source spid37s
> > Message
> > The mirroring connection to "TCP://SQL2:5022" has timed out for database
> > "DB1" after 10 seconds without a response. Check the service and network
> > connections.
> >
> > Date 3/2/2007 2:52:06 PM
> > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > Source spid37s
> > Message
> > Error: 1479, Severity: 16, State: 1.
> >
> >
> > [MIRROR]
> >
> > Date 3/2/2007 2:52:49 PM
> > Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> > Source spid35s
> > Message
> > The mirroring connection to "TCP://SQL1:5022" has timed out for database
> > "DB1" after 5 seconds without a response. Check the service and network
> > connections.
> >
> >
> > Date 3/2/2007 2:52:49 PM
> > Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> > Source spid35s
> > Message
> > Error: 1479, Severity: 16, State: 1.
> >
> >
> > This only occurs for this particular DB. I have mirroring running
> > successfully for 4 other DBs. The only difference I can see is that the
> > problematic DB is significantly larger than the other mirrored DBs... it's
> > ~70GB.
> >
> > I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
> > instances.
> >
> > Please help...
>
>|||Well... I finally got it working. It seemed like the large physical size of
the transaction log file was causing the problem. The log file was 200GB,
but it was only 1% used. I shrunk the log file size back down to 1GB and did
the whole restore/backup process and mirroring started right up.
"slin" wrote:
> Already did a DBCC CHECKDB... No errors. I'm using Profiler to see if it'll
> show me what's failing, but not having any luck so far...
> -S
> "Mark Broadbent" wrote:
> > interesting. cant say I've seen this before but trying running consistancy
> > check DBCC CHECKDB (refer to BOL) perhaps a corruption in the db is causing
> > the timeout.
> >
> > M.
> >
> >
> > "slin" <slin@.discussions.microsoft.com> wrote in message
> > news:E52523C6-0B5C-4507-B6FA-9439EFD1C02E@.microsoft.com...
> > > I'm getting the following errors when trying to set up mirroring for a DB.
> > >
> > > [PRINCIPAL]
> > >
> > > Date 3/2/2007 2:52:06 PM
> > > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > > Source spid99
> > > Message
> > > Communications to the remote server instance 'TCP://SQL2:5022' failed
> > > before
> > > database mirroring was fully started. The ALTER DATABASE command failed.
> > > Retry the command when the remote database is started.
> > >
> > > Date 3/2/2007 2:52:06 PM
> > > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > > Source spid99
> > > Message
> > > Error: 1413, Severity: 16, State: 1.
> > >
> > > Date 3/2/2007 2:52:06 PM
> > > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > > Source spid37s
> > > Message
> > > The mirroring connection to "TCP://SQL2:5022" has timed out for database
> > > "DB1" after 10 seconds without a response. Check the service and network
> > > connections.
> > >
> > > Date 3/2/2007 2:52:06 PM
> > > Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> > > Source spid37s
> > > Message
> > > Error: 1479, Severity: 16, State: 1.
> > >
> > >
> > > [MIRROR]
> > >
> > > Date 3/2/2007 2:52:49 PM
> > > Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> > > Source spid35s
> > > Message
> > > The mirroring connection to "TCP://SQL1:5022" has timed out for database
> > > "DB1" after 5 seconds without a response. Check the service and network
> > > connections.
> > >
> > >
> > > Date 3/2/2007 2:52:49 PM
> > > Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> > > Source spid35s
> > > Message
> > > Error: 1479, Severity: 16, State: 1.
> > >
> > >
> > > This only occurs for this particular DB. I have mirroring running
> > > successfully for 4 other DBs. The only difference I can see is that the
> > > problematic DB is significantly larger than the other mirrored DBs... it's
> > > ~70GB.
> > >
> > > I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
> > > instances.
> > >
> > > Please help...
> >
> >
> >

Cant get CAST function to work in ASP.NET

I'm trying to do something like this SQL statement. I have a table with a field of date/times.

i.e - 2/27/06 9:55:95 PM Basically there are multiple entries in the table per day.

I want to count the records for particular (hence the CAST) and output the count.

Here it was I had just to see if SQL would work in ASP.NET :

SELECT COUNT(*) AS Expr1
FROM dbo.tblActiveDrums
WHERE [CAST](FLOOR([CAST](NCTimeStamp AS [float])) AS datetime) = '0' OR
NCTimeStamp - [CAST](FLOOR([CAST](NCTimeStamp AS [float])) AS datetime) = '0'

It didn't like the AS references?

Any help would be appreciated.

Remove all the brackets and post if there are any error messages. Shouldn't be.|||You want to count the records for a particular what?

cant create object on sql server

When i try to deploy my project or the cube within it i first i get a message 'The server content appears out of date'

then in the error list it tells me 'user does not have permission to create object on [servername] or object does not exist.

Why is this?

Should i create a database first in sql managment studio with a particular name, the name of the project for example. I have tried different impersonation modes...

What login account does analysis services run under when it tries to connect to deploy?

Does it try to create an analysis services database?

Any advise or pointers would be greatly appreciated. Thanks alot.

Jules

The project deployment in BI Dev Studio is happening under your account. You need to have administrative rights ( in many cases ) to deploy your project.

By default all local machine Administrators are also administrators of Analysis Server.

Check check your project properties to see which server you deploy your project to.

You can also open SQL Management studio to see the state your database after your deployed it to Analysis Server.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.