Database Overwritten: restore

Showing posts with label restore. Show all posts

Thursday, March 29, 2012

Database Movement

Hello, I normally use the database backup and restore commands when I am
moving one database for one computer to another. This time however, I
brought over the raw files for the log and data. How can I get sql server
to incorporate these files into the server that I am placing them on. This
server does not have that database at all. I moved the files to the
location it normally places the log and datafiles, but when I brought SQL
server up, it did not show me those files in enterprise manager.
Any ideas how to utilize these files in SQL server?
Thanks in advance for your assistance!!!!!!Look up sp_attach_db and sp_detach_db in BOL (Books On-Line).
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"C_Silin" <OverwhelmedButStillTrying@.hotmail.com> wrote in message
news:Xns9485989199631CSilinhotmailcom@.207.46.248.16...
> Hello, I normally use the database backup and restore commands when I am
> moving one database for one computer to another. This time however, I
> brought over the raw files for the log and data. How can I get sql server
> to incorporate these files into the server that I am placing them on.
This
> server does not have that database at all. I moved the files to the
> location it normally places the log and datafiles, but when I brought SQL
> server up, it did not show me those files in enterprise manager.
> Any ideas how to utilize these files in SQL server?
> Thanks in advance for your assistance!!!!!!

Database Movement

quote:

> Hello, I normally use the database backup and restore commands when I am
> moving one database for one computer to another. This time however, I
> brought over the raw files for the log and data. How can I get sql server
> to incorporate these files into the server that I am placing them on.

This

quote:

> server does not have that database at all. I moved the files to the
> location it normally places the log and datafiles, but when I brought SQL
> server up, it did not show me those files in enterprise manager.
> Any ideas how to utilize these files in SQL server?
> Thanks in advance for your assistance!!!!!!

Tuesday, March 27, 2012

Database 'model' cannot be opened. It is in the middle of a restore

http://support.microsoft.com/kb/822852
how do i run this if my database is msde?I didn't see anything in the article which shouldn't work on msde except for replacing Query
Analyzer with OSQL.EXE.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"nobody" <nobody@.nobody.com> wrote in message news:Ow4degdMIHA.4476@.TK2MSFTNGP06.phx.gbl...
> http://support.microsoft.com/kb/822852
>
> how do i run this if my database is msde?
>

Database 'model' cannot be opened. It is in the middle of a restore

http://support.microsoft.com/kb/822852
how do i run this if my database is msde?I didn't see anything in the article which shouldn't work on msde except for
replacing Query
Analyzer with OSQL.EXE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"nobody" <nobody@.nobody.com> wrote in message news:Ow4degdMIHA.4476@.TK2MSFTNGP06.phx.gbl...[
vbcol=seagreen]
> http://support.microsoft.com/kb/822852
>
> how do i run this if my database is msde?
>[/vbcol]

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

Wednesday, March 21, 2012

Database Mirgration

Hi,
When I do the database migration from one server to another using attach
deattach /backup Restore, do all the users and roles of the database
automatically be migrated as well.
I am under the impression that the users and roles are in Master database.
Do I need to use Transfer Login Task to do the Login Migration?
Thanks
Ed"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:2AE42947-4BAA-4654-BAF7-02C340286E2C@.microsoft.com...
> Hi,
> When I do the database migration from one server to another using attach
> deattach /backup Restore, do all the users and roles of the database
> automatically be migrated as well.
> I am under the impression that the users and roles are in Master
database.
> Do I need to use Transfer Login Task to do the Login Migration?
> Thanks
> Ed
>
The database users and roles will migrate, however the SQL Server logins
will not. You will have to recreate your logins (Windows Authenticated
and/or SQL Authenticated) on the new server.
The Windows Authenticated users will automatically match the id's in the
database, the SQL Authenticated users however will not. You will need to
take a look at the sp_change_users_login in BOL to get those SQL
Authenticated users to match up with the newly created SQL Logins.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||When you attach/detach backup/restore a database, the users and database
roles are of course moved across, as they are stored within the database.
But the logins these database users are linked to, will not be moved, as
they are in the master database.
For more info, on how to troubleshoot this issue, see:
http://vyaskn.tripod.com/troublesho...rphan_users.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:2AE42947-4BAA-4654-BAF7-02C340286E2C@.microsoft.com...
Hi,
When I do the database migration from one server to another using attach
deattach /backup Restore, do all the users and roles of the database
automatically be migrated as well.
I am under the impression that the users and roles are in Master database.
Do I need to use Transfer Login Task to do the Login Migration?
Thanks
Ed|||yes! all the users and roles are migrated to a new server.
but, the logins are not migrated
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
---
"Ed" wrote:

> Hi,
> When I do the database migration from one server to another using attach
> deattach /backup Restore, do all the users and roles of the database
> automatically be migrated as well.
> I am under the impression that the users and roles are in Master databas
e.
> Do I need to use Transfer Login Task to do the Login Migration?
> Thanks
> Ed
>|||Hi,
If you migrate Master database as well then all the Logins, users , Roles
will be migrated to new server. Incase if you are migrating the
Master database then Logins will not get migrated. In that case you could
use Transfer Login Task to do login migration.
Thanks
Hari
SQL Server MVP
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:2AE42947-4BAA-4654-BAF7-02C340286E2C@.microsoft.com...
> Hi,
> When I do the database migration from one server to another using attach
> deattach /backup Restore, do all the users and roles of the database
> automatically be migrated as well.
> I am under the impression that the users and roles are in Master
> database.
> Do I need to use Transfer Login Task to do the Login Migration?
> Thanks
> Ed
>sql

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time o
f
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) o
r
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql...skn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in messag
e
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>sql

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
Rodrigo
Backups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
David Portas
SQL Server MVP
|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo
|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:

> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
>
>

Database Migration

Hello.
I'm going to migrate an entrie SQL Server to a new box. The original plan
was to backup and restore all DBs on the new server, but due the long time of
the backup I'd like to try other way.
I'm thinking of simply offline->copy->attach .MDF to the new server, but as
the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if a
simple attach is risk-free (basically in terms of systables/sysprocedures) or
maybe exist a better way to do it.
What can you advice me?
Thanks
RodrigoBackups should give you much less downtime than you can achieve by
detaching and re-attaching:
1. Database backup on Server A
2. Restore to new Server B
3. Set A to single-user mode
4. Transaction log backup on A
5. Restore transaction log(s) on B
Make sure you read the following article. Particularly the references
to orphaned users:
http://support.microsoft.com/?id=314546
--
David Portas
SQL Server MVP
--|||Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> Hello.
> I'm going to migrate an entrie SQL Server to a new box. The original plan
> was to backup and restore all DBs on the new server, but due the long time
> of
> the backup I'd like to try other way.
> I'm thinking of simply offline->copy->attach .MDF to the new server, but
> as
> the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> a
> simple attach is risk-free (basically in terms of systables/sysprocedures)
> or
> maybe exist a better way to do it.
> What can you advice me?
> Thanks
> Rodrigo|||Thanks David & Narayana; both excellent links.
There they solve the doubt about moving DBs between SQL versions (answer: no
problem).
The orphan users were been considerated too.
Thanks
"Narayana Vyas Kondreddi" wrote:
> Have a look at this article: http://vyaskn.tripod.com/moving_sql_server.htm
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Rodrigo Guerra" <RodrigoGuerra@.discussions.microsoft.com> wrote in message
> news:D364210D-6F34-4806-B58F-6DA671E2A248@.microsoft.com...
> > Hello.
> >
> > I'm going to migrate an entrie SQL Server to a new box. The original plan
> > was to backup and restore all DBs on the new server, but due the long time
> > of
> > the backup I'd like to try other way.
> >
> > I'm thinking of simply offline->copy->attach .MDF to the new server, but
> > as
> > the new server has SQL-SP4 and the old one has SQL-SP3 I wanted to know if
> > a
> > simple attach is risk-free (basically in terms of systables/sysprocedures)
> > or
> > maybe exist a better way to do it.
> >
> > What can you advice me?
> >
> > Thanks
> > Rodrigo
>
>sql

Monday, March 19, 2012

Database marked suspect

My primary database is currently marked suspect. I
believe it could be because the transaction log was
deleted. How can I restore the database to be
operational?
Any assistance is greatly appreciated!use this one sp_resetstatus [ @.DBName =3D ] 'database'
See BOL for more information om the same ...
-- HTH,
Vinod Kumar
MCSE, DBA, MCAD
http://www.extremeexperts.com/
"Michelle" <msarna@.starpower.net> wrote in message =news:042c01c3588e$c42cda60$a401280a@.phx.gbl...
> My primary database is currently marked suspect. I > believe it could be because the transaction log was > deleted. How can I restore the database to be > operational?
> > Any assistance is greatly appreciated!

DATABASE marked "SUSPECT" - How to restore?

Recently after I rebooted the MS SQL server, the "cdr"
database is marked with "Suspect" in the Enterprise
Manager,and when I try to access the database, the
Enterprise Manager prompted that the database is marked
as "Suspect" and inaccessible. When looked into the
MSSQL\data folder, the .MDB file and LDF is still there.
Strongly believe this is because there was a torn page
happened(because I restarted the server when the pc hung).
The cdr database contain our latest 3 months call records
and it is up to 22G of data. The bad new is, no backup had
been done to restore the data. I've tried to use
sp_attach_db, recreate database and all other method to
restore the data, still failed to restore the data. Since
the MDF file is preserved, hopefully there is a method to
restore the database.hey have a look at this website,
http://www.spaceprogram.com/knowledge/sqlserver_recover_fro
m_deleted_log.html
>--Original Message--
>Recently after I rebooted the MS SQL server, the "cdr"
>database is marked with "Suspect" in the Enterprise
>Manager,and when I try to access the database, the
>Enterprise Manager prompted that the database is marked
>as "Suspect" and inaccessible. When looked into the
>MSSQL\data folder, the .MDB file and LDF is still there.
>Strongly believe this is because there was a torn page
>happened(because I restarted the server when the pc
hung).
>The cdr database contain our latest 3 months call records
>and it is up to 22G of data. The bad new is, no backup
had
>been done to restore the data. I've tried to use
>sp_attach_db, recreate database and all other method to
>restore the data, still failed to restore the data. Since
>the MDF file is preserved, hopefully there is a method to
>restore the database.
>.
>|||Hi,
I got these from another newsgroup several months ago and
they have worked on three suspect databases since. I
generally only need to run the DBCC rebuild_log and then
run a DBCC CheckDB to make sure the database is not
corrupt. Hope they help.
1) Make sure you have a copy of your.MDF
2) Create a new database called fake (default file
locations)
3) Stop SQL Service
4) Delete the fake_Data.MDF and copy your.MDF to where
fake_Data.MDF used
to
be and rename the file to fake_Data.MDF
5) Start SQL Service
6) Database fake will appear as suspect in EM
7) Open Query Analyser and in master database run the
following :
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysdatabases set
status=-32768 where dbid=DB_ID('fake')
go
sp_configure 'allow updates',0
go
reconfigure with override
go
This will put the database in emergency recovery mode
8) Stop SQL Service
9) Delete the fake_Log.LDF file
10) Restart SQL Service
11) In QA run the following (with correct path for log)
dbcc rebuild_log('fake','h:\fake_log.ldf')
go
dbcc checkdb('fake') -- to check for errors
go
12) Now we need to rename the files, run the following
(make sure there
are
no connections to it) in Query Analyzer (At this stage
you can actually
access the database so you could use DTS or bcp to move
the data to
another
database).
use master
go
sp_helpdb 'fake'
go
/* Make a note of the names of the files , you will
need them
in the next bit of the script to replace datafilename
and
logfilename - it might be that they have the right
names */
sp_renamedb 'fake','your'
go
alter database your
MODIFY FILE(NAME='datafilename', NEWNAME
= 'your_data')
go
alter database PowerDVD301
MODIFY FILE(NAME='logfilename', NEWNAME
= 'your_Log')
go
dbcc checkdb('your')
go
sp_dboption 'your','dbo use only','false'
go
use PowerDVD301
go
sp_updatestats
go
13) You should now have a working database. However the
log file will be
small so it will be worth increasing its size.
Unfortunately your files
will
be called fake_Data.MDF and fake_Log.LDF but you can get
round this by
detaching thedatabase properly and then renaming the
files and reattaching
it.
14) Run the following in QA
sp_detach_db your
--now rename the files then reattach
sp_attach_db 'your','your.mdf','your.ldf'
>--Original Message--
>Recently after I rebooted the MS SQL server, the "cdr"
>database is marked with "Suspect" in the Enterprise
>Manager,and when I try to access the database, the
>Enterprise Manager prompted that the database is marked
>as "Suspect" and inaccessible. When looked into the
>MSSQL\data folder, the .MDB file and LDF is still there.
>Strongly believe this is because there was a torn page
>happened(because I restarted the server when the pc
hung).
>The cdr database contain our latest 3 months call records
>and it is up to 22G of data. The bad new is, no backup
had
>been done to restore the data. I've tried to use
>sp_attach_db, recreate database and all other method to
>restore the data, still failed to restore the data. Since
>the MDF file is preserved, hopefully there is a method to
>restore the database.
>.
>|||Be warned - rebuilding your log is extremely dangerous and UNSUPPORTED (i.e.
you're on your own when it goes wrong - which it can very easily do).
This command commonly results in large amounts of lost data and, much more
seriously, loss of all transactional consistency in your database (i.e. did
that update transaction to a customer's bank account happen or not? there is
no way to tell).
If your business can cope with that, fine.
Microsoft strongly recommends that you DO NOT use this command or the
procedures documented below.
Regards,
Paul.
--
Paul Randal
DBCC Technical Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Antinore" <wantinore@.veramark.com> wrote in message
news:0e8601c38cc6$5092d840$a301280a@.phx.gbl...
> Hi,
> I got these from another newsgroup several months ago and
> they have worked on three suspect databases since. I
> generally only need to run the DBCC rebuild_log and then
> run a DBCC CheckDB to make sure the database is not
> corrupt. Hope they help.
> 1) Make sure you have a copy of your.MDF
> 2) Create a new database called fake (default file
> locations)
> 3) Stop SQL Service
> 4) Delete the fake_Data.MDF and copy your.MDF to where
> fake_Data.MDF used
> to
> be and rename the file to fake_Data.MDF
> 5) Start SQL Service
> 6) Database fake will appear as suspect in EM
> 7) Open Query Analyser and in master database run the
> following :
> sp_configure 'allow updates',1
> go
> reconfigure with override
> go
> update sysdatabases set
> status=-32768 where dbid=DB_ID('fake')
> go
> sp_configure 'allow updates',0
> go
> reconfigure with override
> go
> This will put the database in emergency recovery mode
> 8) Stop SQL Service
> 9) Delete the fake_Log.LDF file
> 10) Restart SQL Service
> 11) In QA run the following (with correct path for log)
> dbcc rebuild_log('fake','h:\fake_log.ldf')
> go
> dbcc checkdb('fake') -- to check for errors
> go
> 12) Now we need to rename the files, run the following
> (make sure there
> are
> no connections to it) in Query Analyzer (At this stage
> you can actually
> access the database so you could use DTS or bcp to move
> the data to
> another
> database).
> use master
> go
> sp_helpdb 'fake'
> go
> /* Make a note of the names of the files , you will
> need them
> in the next bit of the script to replace datafilename
> and
> logfilename - it might be that they have the right
> names */
> sp_renamedb 'fake','your'
> go
> alter database your
> MODIFY FILE(NAME='datafilename', NEWNAME
> = 'your_data')
> go
> alter database PowerDVD301
> MODIFY FILE(NAME='logfilename', NEWNAME
> = 'your_Log')
> go
> dbcc checkdb('your')
> go
> sp_dboption 'your','dbo use only','false'
> go
> use PowerDVD301
> go
> sp_updatestats
> go
> 13) You should now have a working database. However the
> log file will be
> small so it will be worth increasing its size.
> Unfortunately your files
> will
> be called fake_Data.MDF and fake_Log.LDF but you can get
> round this by
> detaching thedatabase properly and then renaming the
> files and reattaching
> it.
> 14) Run the following in QA
> sp_detach_db your
> --now rename the files then reattach
> sp_attach_db 'your','your.mdf','your.ldf'
>
> >--Original Message--
> >Recently after I rebooted the MS SQL server, the "cdr"
> >database is marked with "Suspect" in the Enterprise
> >Manager,and when I try to access the database, the
> >Enterprise Manager prompted that the database is marked
> >as "Suspect" and inaccessible. When looked into the
> >MSSQL\data folder, the .MDB file and LDF is still there.
> >Strongly believe this is because there was a torn page
> >happened(because I restarted the server when the pc
> hung).
> >The cdr database contain our latest 3 months call records
> >and it is up to 22G of data. The bad new is, no backup
> had
> >been done to restore the data. I've tried to use
> >sp_attach_db, recreate database and all other method to
> >restore the data, still failed to restore the data. Since
> >the MDF file is preserved, hopefully there is a method to
> >restore the database.
> >.
> >

Friday, February 17, 2012

Database loading..

Hello,
We did a restore of a database to a test database, however after the restore
the database is still showing as loading. I was not present during the
restore but it looks like the norecovery option was not used. We tried the
database restore dbname recovery option but that did not work. We also tried
rebooting and restarting the services. Any suggestions?Is it just a refresh issue in the GUI? If no, did you receive an error from the:
RESTORE DATABASE dbname WITH RECOVERY
What was the exact error message, if any was returned.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Lina" <Lina@.discussions.microsoft.com> wrote in message
news:51ACE18B-F4B4-4ED2-A899-3BCE829D327B@.microsoft.com...
> Hello,
> We did a restore of a database to a test database, however after the restore
> the database is still showing as loading. I was not present during the
> restore but it looks like the norecovery option was not used. We tried the
> database restore dbname recovery option but that did not work. We also tried
> rebooting and restarting the services. Any suggestions?|||Do you mean the error message in SQL Query Analyzer after the restore
database dbname recovery?
"Tibor Karaszi" wrote:
> Is it just a refresh issue in the GUI? If no, did you receive an error from the:
> RESTORE DATABASE dbname WITH RECOVERY
> What was the exact error message, if any was returned.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Lina" <Lina@.discussions.microsoft.com> wrote in message
> news:51ACE18B-F4B4-4ED2-A899-3BCE829D327B@.microsoft.com...
> > Hello,
> >
> > We did a restore of a database to a test database, however after the restore
> > the database is still showing as loading. I was not present during the
> > restore but it looks like the norecovery option was not used. We tried the
> > database restore dbname recovery option but that did not work. We also tried
> > rebooting and restarting the services. Any suggestions?
>|||Yes
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Lina" <Lina@.discussions.microsoft.com> wrote in message
news:F9EAECB4-269A-4F20-AC9A-6810FC9F5F7D@.microsoft.com...
> Do you mean the error message in SQL Query Analyzer after the restore
> database dbname recovery?
> "Tibor Karaszi" wrote:
>> Is it just a refresh issue in the GUI? If no, did you receive an error from the:
>> RESTORE DATABASE dbname WITH RECOVERY
>> What was the exact error message, if any was returned.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Lina" <Lina@.discussions.microsoft.com> wrote in message
>> news:51ACE18B-F4B4-4ED2-A899-3BCE829D327B@.microsoft.com...
>> > Hello,
>> >
>> > We did a restore of a database to a test database, however after the restore
>> > the database is still showing as loading. I was not present during the
>> > restore but it looks like the norecovery option was not used. We tried the
>> > database restore dbname recovery option but that did not work. We also tried
>> > rebooting and restarting the services. Any suggestions?
>>|||We get error 4331.
"Tibor Karaszi" wrote:
> Yes
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Lina" <Lina@.discussions.microsoft.com> wrote in message
> news:F9EAECB4-269A-4F20-AC9A-6810FC9F5F7D@.microsoft.com...
> > Do you mean the error message in SQL Query Analyzer after the restore
> > database dbname recovery?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Is it just a refresh issue in the GUI? If no, did you receive an error from the:
> >> RESTORE DATABASE dbname WITH RECOVERY
> >>
> >> What was the exact error message, if any was returned.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Lina" <Lina@.discussions.microsoft.com> wrote in message
> >> news:51ACE18B-F4B4-4ED2-A899-3BCE829D327B@.microsoft.com...
> >> > Hello,
> >> >
> >> > We did a restore of a database to a test database, however after the restore
> >> > the database is still showing as loading. I was not present during the
> >> > restore but it looks like the norecovery option was not used. We tried the
> >> > database restore dbname recovery option but that did not work. We also tried
> >> > rebooting and restarting the services. Any suggestions?
> >>
> >>
>|||Hi Lina
Even though some of us have been using SQL Server for many years, most of us
don't memorize error numbers. After 19 years, I know 1205 and 208.
It would be helpful if you could also let us know the text of the error
message.
Also, can you show us the exact command used?
The more info you can provide about exactly what steps you took and what the
results/response was, the more help we can provide.
Thanks
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Lina" <Lina@.discussions.microsoft.com> wrote in message
news:D2939914-B7CF-4C7E-8D84-A5BF7FD73998@.microsoft.com...
> We get error 4331.
> "Tibor Karaszi" wrote:
>> Yes
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Lina" <Lina@.discussions.microsoft.com> wrote in message
>> news:F9EAECB4-269A-4F20-AC9A-6810FC9F5F7D@.microsoft.com...
>> > Do you mean the error message in SQL Query Analyzer after the restore
>> > database dbname recovery?
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Is it just a refresh issue in the GUI? If no, did you receive an error
>> >> from the:
>> >> RESTORE DATABASE dbname WITH RECOVERY
>> >>
>> >> What was the exact error message, if any was returned.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "Lina" <Lina@.discussions.microsoft.com> wrote in message
>> >> news:51ACE18B-F4B4-4ED2-A899-3BCE829D327B@.microsoft.com...
>> >> > Hello,
>> >> >
>> >> > We did a restore of a database to a test database, however after the
>> >> > restore
>> >> > the database is still showing as loading. I was not present during
>> >> > the
>> >> > restore but it looks like the norecovery option was not used. We
>> >> > tried the
>> >> > database restore dbname recovery option but that did not work. We
>> >> > also tried
>> >> > rebooting and restarting the services. Any suggestions?
>> >>
>> >>
>>|||BOL sez:
4331 16 The database cannot be recovered because the files have been
restored to inconsistent points in time.
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\trblsql.chm::/tr_syserrors1a_81o9.htm
J.
On Fri, 29 Sep 2006 13:56:57 -0700, "Kalen Delaney"
<replies@.public_newsgroups.com> wrote:
>Hi Lina
>Even though some of us have been using SQL Server for many years, most of us
>don't memorize error numbers. After 19 years, I know 1205 and 208.
>It would be helpful if you could also let us know the text of the error
>message.
>Also, can you show us the exact command used?
>The more info you can provide about exactly what steps you took and what the
>results/response was, the more help we can provide.
>Thanks|||That is a new one to me. I guess Lina is best served by re-doing the restore or opening a ticket
with MS Support if the problem persists.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
news:jblrh21bd2vrf50ioill727cnsu4v8308g@.4ax.com...
> BOL sez:
> 4331 16 The database cannot be recovered because the files have been
> restored to inconsistent points in time.
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\trblsql.chm::/tr_syserrors1a_81o9.htm
> J.
>
> On Fri, 29 Sep 2006 13:56:57 -0700, "Kalen Delaney"
> <replies@.public_newsgroups.com> wrote:
>>Hi Lina
>>Even though some of us have been using SQL Server for many years, most of us
>>don't memorize error numbers. After 19 years, I know 1205 and 208.
>>It would be helpful if you could also let us know the text of the error
>>message.
>>Also, can you show us the exact command used?
>>The more info you can provide about exactly what steps you took and what the
>>results/response was, the more help we can provide.
>>Thanks
>

'Database Loading' state after Restore

Hi,
I have a Windows Server 2003 cluster setup with 3 SQL
Server 2000 virtual servers installed. When I perform a
restore of an 85 GB database, the database gets stuck in
a 'Database Loading' state. It doesn't appear to be a
resource issue since SQL has access to all 8 processors
and 4 GB of memory and the system is not under stress. I
have checked the SQL and Event Viewer logs for clues but
have found nothing to pursue. Any assistance is greatly
appreciated.
Sincerely,
ABGABG,
Did you get a message that the database restore finished
successfully (even though it is 'loading' state')?
During the restore process, you must the with 'RECOVERY'
OPTION.
If the restore is finished, you could do the following to
recover the database:
RESTORE DATABASE_NAME
WITH RECOVERY
hth
DeeJay
>--Original Message--
>Hi,
> I have a Windows Server 2003 cluster setup with 3 SQL
>Server 2000 virtual servers installed. When I perform a
>restore of an 85 GB database, the database gets stuck in
>a 'Database Loading' state. It doesn't appear to be a
>resource issue since SQL has access to all 8 processors
>and 4 GB of memory and the system is not under stress. I
>have checked the SQL and Event Viewer logs for clues but
>have found nothing to pursue. Any assistance is greatly
>appreciated.
> Sincerely,
> ABG
>.
>|||Yes, it stated that the recovery completed. Although the
database stayed in Loading state. I'm running the restore
from Enterprise Manager, is there a way to specify
the 'Recovery' option from here? Or must the restore be
performed from Query Analyzer? Thank you for your reply.
Sincerely,
ABG
>--Original Message--
>ABG,
>Did you get a message that the database restore finished
>successfully (even though it is 'loading' state')?
>During the restore process, you must the with 'RECOVERY'
>OPTION.
>If the restore is finished, you could do the following to
>recover the database:
>RESTORE DATABASE_NAME
>WITH RECOVERY
>hth
>DeeJay
>>--Original Message--
>>Hi,
>> I have a Windows Server 2003 cluster setup with 3 SQL
>>Server 2000 virtual servers installed. When I perform a
>>restore of an 85 GB database, the database gets stuck in
>>a 'Database Loading' state. It doesn't appear to be a
>>resource issue since SQL has access to all 8 processors
>>and 4 GB of memory and the system is not under stress. I
>>have checked the SQL and Event Viewer logs for clues but
>>have found nothing to pursue. Any assistance is greatly
>>appreciated.
>> Sincerely,
>> ABG
>>.
>.
>|||In EM, right.most tab (at the bottom), you have option for
RECOVERY/NORECOVERY/STANDBY. Default is, however RECOVERY on the last backup
(the topmost alternative). The command shown by DeeJay to recovery without
doing an actual restore is not available from EM.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"ABG" <anonymous@.discussions.microsoft.com> wrote in message
news:03c101c3a8a0$d4e30f70$a401280a@.phx.gbl...
> Yes, it stated that the recovery completed. Although the
> database stayed in Loading state. I'm running the restore
> from Enterprise Manager, is there a way to specify
> the 'Recovery' option from here? Or must the restore be
> performed from Query Analyzer? Thank you for your reply.
> Sincerely,
> ABG
> >--Original Message--
> >ABG,
> >
> >Did you get a message that the database restore finished
> >successfully (even though it is 'loading' state')?
> >
> >During the restore process, you must the with 'RECOVERY'
> >OPTION.
> >
> >If the restore is finished, you could do the following to
> >recover the database:
> >
> >RESTORE DATABASE_NAME
> >WITH RECOVERY
> >
> >hth
> >
> >DeeJay
> >>--Original Message--
> >>Hi,
> >> I have a Windows Server 2003 cluster setup with 3 SQL
> >>Server 2000 virtual servers installed. When I perform a
> >>restore of an 85 GB database, the database gets stuck in
> >>a 'Database Loading' state. It doesn't appear to be a
> >>resource issue since SQL has access to all 8 processors
> >>and 4 GB of memory and the system is not under stress. I
> >>have checked the SQL and Event Viewer logs for clues but
> >>have found nothing to pursue. Any assistance is greatly
> >>appreciated.
> >> Sincerely,
> >> ABG
> >>
> >>.
> >>
> >.
> >

Tuesday, February 14, 2012

'Database Loading' state after Restore

I have a SQL 2000 Ent. SP3 on W2k3 cluster.
Every time when I restore a db from EM ( Use : leave database operational ...) it starts restoring, I se NO progression on the progressbar, and then it says: Successfully restored ...
And the db is gray and says Loading. I cant acess it in any way. No errors in any logs.
The db I now have problem with restores ok on another system.
I havent had this problem with small db's. The one I'm trying now is 9GB.try RESTORE DATABASE ... WITH RECOVERY option
"Bjørn" <anonymous@.discussions.microsoft.com> wrote in message
news:6DDC2092-7FCC-4C57-9759-812AAA5CEB84@.microsoft.com...
> I have a SQL 2000 Ent. SP3 on W2k3 cluster.
> Every time when I restore a db from EM ( Use : leave database operational
...) it starts restoring, I se NO progression on the progressbar, and then
it says: Successfully restored ...
> And the db is gray and says Loading. I cant acess it in any way. No errors
in any logs.
> The db I now have problem with restores ok on another system.
> I havent had this problem with small db's. The one I'm trying now is 9GB.
>
>|||Says :
File 'db_data' was only partially restored by a database or file restore. The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
And trying to get the properties of the db says:
Error 927. Database '...' cannot be opened. It is in the middle of a restore.

'Database Loading' state after Restore

quote:

> I have a SQL 2000 Ent. SP3 on W2k3 cluster.
> Every time when I restore a db from EM ( Use : leave database operational

...) it starts restoring, I se NO progression on the progressbar, and then
it says: Successfully restored ...

quote:

> And the db is gray and says Loading. I cant acess it in any way. No errors

in any logs.

quote:

> The db I now have problem with restores ok on another system.
> I havent had this problem with small db's. The one I'm trying now is 9GB.
>
>

|||Says :
File 'db_data' was only partially restored by a database or file restore. Th
e entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
And trying to get the properties of the db says:
Error 927. Database '...' cannot be opened. It is in the middle of a restor
e.

Database keeps loading - urgent !

I'm trying to restore a set of 4 different databases. 2 of them went ok but
the 2 others keep 'loading' after a succesfull restore ( with NORECOVERY
option). When I try the RECOVER option I get this message
Server: Msg 3624, Level 20, State 1, Line 1
Location: filemgr.cpp:1749
Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON (FCB_DROPPED,
saflStatus)
SPID: 57
Process ID: 1604
Connection Broken
What can I do to resolve this problem ? I really need this data !Freddy
Drop the loading database and restore a new one with RECOVERY option
"Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
message news:D694FB64-05DE-460B-A73C-37AAF856D1F7@.microsoft.com...
> I'm trying to restore a set of 4 different databases. 2 of them went ok
but
> the 2 others keep 'loading' after a succesfull restore ( with NORECOVERY
> option). When I try the RECOVER option I get this message
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: filemgr.cpp:1749
> Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON (FCB_DROPPED,
> saflStatus)
> SPID: 57
> Process ID: 1604
> Connection Broken
> What can I do to resolve this problem ? I really need this data !|||I tried it with option RECOVER and that is when I get the error message
mentioned in my first question. Other options ?
Thanks
"Uri Dimant" wrote:
> Freddy
> Drop the loading database and restore a new one with RECOVERY option
>
> "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
> message news:D694FB64-05DE-460B-A73C-37AAF856D1F7@.microsoft.com...
> > I'm trying to restore a set of 4 different databases. 2 of them went ok
> but
> > the 2 others keep 'loading' after a succesfull restore ( with NORECOVERY
> > option). When I try the RECOVER option I get this message
> > Server: Msg 3624, Level 20, State 1, Line 1
> >
> > Location: filemgr.cpp:1749
> > Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON (FCB_DROPPED,
> > saflStatus)
> > SPID: 57
> > Process ID: 1604
> >
> > Connection Broken
> >
> > What can I do to resolve this problem ? I really need this data !
>
>|||Hi
Is it something that someone removed the log file ?
Try detach the database and then attach it with single file option. (see
BOL)
"Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
message news:53DA351E-5EF0-484A-94D9-4424B14B9CE9@.microsoft.com...
> I tried it with option RECOVER and that is when I get the error message
> mentioned in my first question. Other options ?
> Thanks
> "Uri Dimant" wrote:
> > Freddy
> > Drop the loading database and restore a new one with RECOVERY option
> >
> >
> >
> > "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
> > message news:D694FB64-05DE-460B-A73C-37AAF856D1F7@.microsoft.com...
> > > I'm trying to restore a set of 4 different databases. 2 of them went
ok
> > but
> > > the 2 others keep 'loading' after a succesfull restore ( with
NORECOVERY
> > > option). When I try the RECOVER option I get this message
> > > Server: Msg 3624, Level 20, State 1, Line 1
> > >
> > > Location: filemgr.cpp:1749
> > > Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON (FCB_DROPPED,
> > > saflStatus)
> > > SPID: 57
> > > Process ID: 1604
> > >
> > > Connection Broken
> > >
> > > What can I do to resolve this problem ? I really need this data !
> >
> >
> >|||The log file is there. I tried to attach the file like you said and got this
error
Server: Msg 9003, Level 20, State 6, Line 1
The LSN (1514:1035:8) passed to log scan in database 'BPW_Repository' is
invalid.
Connection Broken
"Uri Dimant" wrote:
> Hi
> Is it something that someone removed the log file ?
> Try detach the database and then attach it with single file option. (see
> BOL)
>
>
> "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
> message news:53DA351E-5EF0-484A-94D9-4424B14B9CE9@.microsoft.com...
> > I tried it with option RECOVER and that is when I get the error message
> > mentioned in my first question. Other options ?
> > Thanks
> >
> > "Uri Dimant" wrote:
> >
> > > Freddy
> > > Drop the loading database and restore a new one with RECOVERY option
> > >
> > >
> > >
> > > "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
> > > message news:D694FB64-05DE-460B-A73C-37AAF856D1F7@.microsoft.com...
> > > > I'm trying to restore a set of 4 different databases. 2 of them went
> ok
> > > but
> > > > the 2 others keep 'loading' after a succesfull restore ( with
> NORECOVERY
> > > > option). When I try the RECOVER option I get this message
> > > > Server: Msg 3624, Level 20, State 1, Line 1
> > > >
> > > > Location: filemgr.cpp:1749
> > > > Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON (FCB_DROPPED,
> > > > saflStatus)
> > > > SPID: 57
> > > > Process ID: 1604
> > > >
> > > > Connection Broken
> > > >
> > > > What can I do to resolve this problem ? I really need this data !
> > >
> > >
> > >
>
>|||Freddy
Look at this article
http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
"Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
message news:2C86E47A-E4B1-46CB-813B-AE6457E71EDF@.microsoft.com...
> The log file is there. I tried to attach the file like you said and got
this
> error
> Server: Msg 9003, Level 20, State 6, Line 1
> The LSN (1514:1035:8) passed to log scan in database 'BPW_Repository' is
> invalid.
> Connection Broken
>
> "Uri Dimant" wrote:
> > Hi
> > Is it something that someone removed the log file ?
> >
> > Try detach the database and then attach it with single file option. (see
> > BOL)
> >
> >
> >
> >
> >
> > "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote in
> > message news:53DA351E-5EF0-484A-94D9-4424B14B9CE9@.microsoft.com...
> > > I tried it with option RECOVER and that is when I get the error
message
> > > mentioned in my first question. Other options ?
> > > Thanks
> > >
> > > "Uri Dimant" wrote:
> > >
> > > > Freddy
> > > > Drop the loading database and restore a new one with RECOVERY option
> > > >
> > > >
> > > >
> > > > "Freddy Lallemand" <FreddyLallemand@.discussions.microsoft.com> wrote
in
> > > > message news:D694FB64-05DE-460B-A73C-37AAF856D1F7@.microsoft.com...
> > > > > I'm trying to restore a set of 4 different databases. 2 of them
went
> > ok
> > > > but
> > > > > the 2 others keep 'loading' after a succesfull restore ( with
> > NORECOVERY
> > > > > option). When I try the RECOVER option I get this message
> > > > > Server: Msg 3624, Level 20, State 1, Line 1
> > > > >
> > > > > Location: filemgr.cpp:1749
> > > > > Expression: IS_ON (FCB_LOG_DEVICE, saflStatus) || IS_ON
(FCB_DROPPED,
> > > > > saflStatus)
> > > > > SPID: 57
> > > > > Process ID: 1604
> > > > >
> > > > > Connection Broken
> > > > >
> > > > > What can I do to resolve this problem ? I really need this data !
> > > >
> > > >
> > > >
> >
> >
> >

Thursday, March 29, 2012

Database Movement

Database Movement

Tuesday, March 27, 2012

Database 'model' cannot be opened. It is in the middle of a restore

Database 'model' cannot be opened. It is in the middle of a restore

database mirroring... restore issue

Wednesday, March 21, 2012

Database Mirgration

Database Migration

Database Migration

Database Migration

Monday, March 19, 2012

Database marked suspect

DATABASE marked "SUSPECT" - How to restore?

Friday, February 17, 2012

Database loading..

Database loading..

Database loading..

'Database Loading' state after Restore

Tuesday, February 14, 2012

'Database Loading' state after Restore

'Database Loading' state after Restore

Database keeps loading - urgent !

Database keeps loading - urgent !

Database keeps loading - urgent !

Database Overwritten

Blog Archive

About Me