database mirroring... restore issue

I'm setting it up using the directions provided by Microsoft @.
http://msdn2.microsoft.com/en-us/library/ms189047.aspx
The problem I originally ran into was exactly like the one mentioned in the
following posting:
http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-us/default.mspx?&query=mirroring&lang=en&cr=US&guid=&sloc=en-US&dg=microsoft.public.sqlserver.clustering&p=1&tid=95381f96-a34a-4d99-9e31-12719452a11d
I found an article online stating that this can occur of your principle
backup wasn't restored to the mirror server in NO RECOVERY mode. I missed
that step when performing the first restore, so i deleted that database and
started over using the NO RECOVERY option on the mirror restore.
The problem I've run into now is that after my restore executes and
completes, the database remains in a (Restoring...) state and never becomes
accessible.
Anyone know what causes this?
Thank you,
- Tyler> The problem I've run into now is that after my restore executes and
> completes, the database remains in a (Restoring...) state and never becomes
> accessible.
This is expected. The mirror database *is* inaccessible. After you have done your ALTER DATABASE SET
PARTNER, you should see some other status, but the database is still inaccessible.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tyler McLaughlin" <TylerMcLaughlin@.discussions.microsoft.com> wrote in message
news:C26DD0C5-1726-4732-B0AA-AAD302D86782@.microsoft.com...
> I'm setting it up using the directions provided by Microsoft @.
> http://msdn2.microsoft.com/en-us/library/ms189047.aspx
> The problem I originally ran into was exactly like the one mentioned in the
> following posting:
> http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-us/default.mspx?&query=mirroring&lang=en&cr=US&guid=&sloc=en-US&dg=microsoft.public.sqlserver.clustering&p=1&tid=95381f96-a34a-4d99-9e31-12719452a11d
> I found an article online stating that this can occur of your principle
> backup wasn't restored to the mirror server in NO RECOVERY mode. I missed
> that step when performing the first restore, so i deleted that database and
> started over using the NO RECOVERY option on the mirror restore.
> The problem I've run into now is that after my restore executes and
> completes, the database remains in a (Restoring...) state and never becomes
> accessible.
> Anyone know what causes this?
> Thank you,
> - Tyler|||If you are looking for a "Hot Standby" (Automatic Failover\Failback)
solution and use the target server as a report server at the same time, then
you must use SQL Server Active\Active Cluster. You can not access a Mirrored
database unless you use Database Snaphosts of that mirrored database. And
this Database Snapshot thing is only possible with SQL Server 2005
Enterprise Edition.
If you say "Warm Standby (Manual Failover) would be OK for me" then go with
Transactional Replication. And you'll be able to use your replicated
database as a report server.
You can also use Log Shipping using Standby recovery state (instead of
NORECOVERY) but then you'd have to kick out all connections\users every time
before applying new transaction logs that shipped from the Primary. By the
way, this is also called as a Warm Standby solution.
--
Ekrem Ã?nsoy
"Tyler McLaughlin" <TylerMcLaughlin@.discussions.microsoft.com> wrote in
message news:C26DD0C5-1726-4732-B0AA-AAD302D86782@.microsoft.com...
> I'm setting it up using the directions provided by Microsoft @.
> http://msdn2.microsoft.com/en-us/library/ms189047.aspx
> The problem I originally ran into was exactly like the one mentioned in
> the
> following posting:
> http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-us/default.mspx?&query=mirroring&lang=en&cr=US&guid=&sloc=en-US&dg=microsoft.public.sqlserver.clustering&p=1&tid=95381f96-a34a-4d99-9e31-12719452a11d
> I found an article online stating that this can occur of your principle
> backup wasn't restored to the mirror server in NO RECOVERY mode. I missed
> that step when performing the first restore, so i deleted that database
> and
> started over using the NO RECOVERY option on the mirror restore.
> The problem I've run into now is that after my restore executes and
> completes, the database remains in a (Restoring...) state and never
> becomes
> accessible.
> Anyone know what causes this?
> Thank you,
> - Tyler