Record Locks: running

Showing posts with label running. Show all posts

Friday, March 23, 2012

recovering from a clustered node failure

We are running SQL Server 2000 and we had a node failure
on one of our secondary nodes. The node was evicted from
the cluster, and the hardware was rebuilt. When we try to
re-setup the node, we follow the steps listed below.
1. Insert the SQL Server 2000 Enterprise Edition compact
disc in your CD-ROM drive. Select Install SQL Server 2000
Components.
2. Click Install SQL Server 2000 Components, click Install
Database Server, and then click Next.
3. On the Computer Name dialog box, select Virtual Server,
and enter the name of an existing clustered instance of
SQL Server 2000.
4. On the Installation Selection dialog box, select
Advanced options, and then click Next.
5. On the Advanced Options dialog box, select Maintain a
Virtual Server for Failover Clustering, and then click
Next.
6. On the Failover Clustering dialog box, click Next.
7. On the Cluster Management dialog box, select node 2 to
add back into the cluster so that both your nodes show up
on the right pane window.
8. On the Remote Information dialog box, enter the user
name and password for the domain administrator account
used for the clustered instance of SQL Server 2000, and
then click Next.
9. When the process is complete, click Finish.
Having clicked Next after step 8, the installation just
dissappears and SQL never gets installed on the secondary
node. Any thoughts?
Also - can you confirm that it's possible to recover a node without having to de-install the virtual servers (active/active setup) and re-install, as this would mean extended outage on the databases..
Thanks indeed.
Yes, you can recover from a node failure. There are precise step-by-step
instructions in BOL for exactly this scenario. Look under 'Maintaining a
Failover Cluster' for Recovering from Failover Cluster Failure. The key
step that you may have to redo is to run the install app to remove the
failed node from the SQL virtual server. This is in addition to the node
eviction and replacemnet you have already done. Once the node is
uninstalled, you can then install SQL on the replacement node.
You can also re-apply Service packs to the new node only without taking the
Virtual SQL instance offline. Check the Service Pack README file for
details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Martyn Cavett" <anonymous@.discussions.microsoft.com> wrote in message
news:8D25D32F-7ECF-4BCC-8827-BFBE4D973844@.microsoft.com...
> We are running SQL Server 2000 and we had a node failure
> on one of our secondary nodes. The node was evicted from
> the cluster, and the hardware was rebuilt. When we try to
> re-setup the node, we follow the steps listed below.
> 1. Insert the SQL Server 2000 Enterprise Edition compact
> disc in your CD-ROM drive. Select Install SQL Server 2000
> Components.
> 2. Click Install SQL Server 2000 Components, click Install
> Database Server, and then click Next.
> 3. On the Computer Name dialog box, select Virtual Server,
> and enter the name of an existing clustered instance of
> SQL Server 2000.
> 4. On the Installation Selection dialog box, select
> Advanced options, and then click Next.
> 5. On the Advanced Options dialog box, select Maintain a
> Virtual Server for Failover Clustering, and then click
> Next.
> 6. On the Failover Clustering dialog box, click Next.
> 7. On the Cluster Management dialog box, select node 2 to
> add back into the cluster so that both your nodes show up
> on the right pane window.
> 8. On the Remote Information dialog box, enter the user
> name and password for the domain administrator account
> used for the clustered instance of SQL Server 2000, and
> then click Next.
> 9. When the process is complete, click Finish.
> Having clicked Next after step 8, the installation just
> dissappears and SQL never gets installed on the secondary
> node. Any thoughts?
> Also - can you confirm that it's possible to recover a node without having
to de-install the virtual servers (active/active setup) and re-install, as
this would mean extended outage on the databases..
> Thanks indeed.
>

recovering from a clustered node failure

We are running SQL Server 2000 and we had a node failure
on one of our secondary nodes. The node was evicted from
the cluster, and the hardware was rebuilt. When we try to
re-setup the node, we follow the steps listed below.
1. Insert the SQL Server 2000 Enterprise Edition compact
disc in your CD-ROM drive. Select Install SQL Server 2000
Components.
2. Click Install SQL Server 2000 Components, click Install
Database Server, and then click Next.
3. On the Computer Name dialog box, select Virtual Server,
and enter the name of an existing clustered instance of
SQL Server 2000.
4. On the Installation Selection dialog box, select
Advanced options, and then click Next.
5. On the Advanced Options dialog box, select Maintain a
Virtual Server for Failover Clustering, and then click
Next.
6. On the Failover Clustering dialog box, click Next.
7. On the Cluster Management dialog box, select node 2 to
add back into the cluster so that both your nodes show up
on the right pane window.
8. On the Remote Information dialog box, enter the user
name and password for the domain administrator account
used for the clustered instance of SQL Server 2000, and
then click Next.
9. When the process is complete, click Finish.
Having clicked Next after step 8, the installation just
dissappears and SQL never gets installed on the secondary
node. Any thoughts?
Also - can you confirm that it's possible to recover a node without having t
o de-install the virtual servers (active/active setup) and re-install, as th
is would mean extended outage on the databases..
Thanks indeed.Yes, you can recover from a node failure. There are precise step-by-step
instructions in BOL for exactly this scenario. Look under 'Maintaining a
Failover Cluster' for Recovering from Failover Cluster Failure. The key
step that you may have to redo is to run the install app to remove the
failed node from the SQL virtual server. This is in addition to the node
eviction and replacemnet you have already done. Once the node is
uninstalled, you can then install SQL on the replacement node.
You can also re-apply Service packs to the new node only without taking the
Virtual SQL instance offline. Check the Service Pack README file for
details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Martyn Cavett" <anonymous@.discussions.microsoft.com> wrote in message
news:8D25D32F-7ECF-4BCC-8827-BFBE4D973844@.microsoft.com...
> We are running SQL Server 2000 and we had a node failure
> on one of our secondary nodes. The node was evicted from
> the cluster, and the hardware was rebuilt. When we try to
> re-setup the node, we follow the steps listed below.
> 1. Insert the SQL Server 2000 Enterprise Edition compact
> disc in your CD-ROM drive. Select Install SQL Server 2000
> Components.
> 2. Click Install SQL Server 2000 Components, click Install
> Database Server, and then click Next.
> 3. On the Computer Name dialog box, select Virtual Server,
> and enter the name of an existing clustered instance of
> SQL Server 2000.
> 4. On the Installation Selection dialog box, select
> Advanced options, and then click Next.
> 5. On the Advanced Options dialog box, select Maintain a
> Virtual Server for Failover Clustering, and then click
> Next.
> 6. On the Failover Clustering dialog box, click Next.
> 7. On the Cluster Management dialog box, select node 2 to
> add back into the cluster so that both your nodes show up
> on the right pane window.
> 8. On the Remote Information dialog box, enter the user
> name and password for the domain administrator account
> used for the clustered instance of SQL Server 2000, and
> then click Next.
> 9. When the process is complete, click Finish.
> Having clicked Next after step 8, the installation just
> dissappears and SQL never gets installed on the secondary
> node. Any thoughts?
> Also - can you confirm that it's possible to recover a node without having
to de-install the virtual servers (active/active setup) and re-install, as
this would mean extended outage on the databases..
> Thanks indeed.
>

Wednesday, March 21, 2012

recovering database from expired trial version

Dear SQL Server experts,
I'm in a little pickle here, and hope I can avoid trashing many hours of
work. Here's the scenario:
I was running SQL Server 7 on Win2K Server, with several database projects
in development . I installed the 120-day trial version of SQL2000 with the
intention of installing Windows Small Business Server 2003 Premium (which
includes licensed SQL2000) before the end of the trial period. Well, the 120
days came and went, and the SQL2000 installation will, of course, no longer
run. The databases that had been converted to SQL2000 and further developed
were not detached or recently backed up prior to the expiration.
I fear that just installing the new OS with SQL2000 may result in the
permanent loss of the work since last backup. If there's a way to
re-activate the existing SQL2000 installation, hopefully without purchasing
the standard stand-alone SQL2000, my work may be saved. Any recommendations
for a course of action would be appreciated.
Thank you.Hi,
I think you should not use trial versions for business purposes. I know
most of us do it but you should not say it in public. try to keep it a
secret...|||Hi,
i would suggest you to uninstall the SQL Server trial version and purchase a
licensed copy.
you just need to install the licensed copy of SQL Server.
After that, you may need to locate your data file (for your previous database)
(For example: C:\program files\Microsoft SQL Server\MSSQL\Data)
Then, open your Enterprise Manager, attach the database file.
hope this will help.
Leo
"Paul Deneen" wrote:
> Dear SQL Server experts,
> I'm in a little pickle here, and hope I can avoid trashing many hours of
> work. Here's the scenario:
> I was running SQL Server 7 on Win2K Server, with several database projects
> in development . I installed the 120-day trial version of SQL2000 with the
> intention of installing Windows Small Business Server 2003 Premium (which
> includes licensed SQL2000) before the end of the trial period. Well, the 120
> days came and went, and the SQL2000 installation will, of course, no longer
> run. The databases that had been converted to SQL2000 and further developed
> were not detached or recently backed up prior to the expiration.
> I fear that just installing the new OS with SQL2000 may result in the
> permanent loss of the work since last backup. If there's a way to
> re-activate the existing SQL2000 installation, hopefully without purchasing
> the standard stand-alone SQL2000, my work may be saved. Any recommendations
> for a course of action would be appreciated.
> Thank you.
>
>|||Mr. Leong,
Thank you. I didn't think that a database could be attached to a SQL
Server installation unless it had previously been "detached" with
sp_detach_db or had been backed up. I have always found it necessary to
detach the db in order to make a MDF file portable.
You don't have any reservations about recommending me to go ahead and
uninstall the trial SQL2000?
Thanks again.
"Leo Leong" wrote:
> Hi,
> i would suggest you to uninstall the SQL Server trial version and purchase a
> licensed copy.
> you just need to install the licensed copy of SQL Server.
> After that, you may need to locate your data file (for your previous database)
> (For example: C:\program files\Microsoft SQL Server\MSSQL\Data)
> Then, open your Enterprise Manager, attach the database file.
> hope this will help.
> Leo
> "Paul Deneen" wrote:
> >
> > Dear SQL Server experts,
> >
> > I'm in a little pickle here, and hope I can avoid trashing many hours of
> > work. Here's the scenario:
> > I was running SQL Server 7 on Win2K Server, with several database projects
> > in development . I installed the 120-day trial version of SQL2000 with the
> > intention of installing Windows Small Business Server 2003 Premium (which
> > includes licensed SQL2000) before the end of the trial period. Well, the 120
> > days came and went, and the SQL2000 installation will, of course, no longer
> > run. The databases that had been converted to SQL2000 and further developed
> > were not detached or recently backed up prior to the expiration.
> >
> > I fear that just installing the new OS with SQL2000 may result in the
> > permanent loss of the work since last backup. If there's a way to
> > re-activate the existing SQL2000 installation, hopefully without purchasing
> > the standard stand-alone SQL2000, my work may be saved. Any recommendations
> > for a course of action would be appreciated.
> >
> > Thank you.
> >
> >
> >|||Hi,
Since your MDF file is still there, you should be able to attach it after
installation.
I have tried once with no problem at all. unless those user logins in my MDF
didn't exist in the database server that I attached to.
May be you have other input. Would you like to share? thanks.
Uninstallation of your current trial version is neccesary. For development,
normally I will get a Developer Edition of SQL Server.
Leo
"Paul Deneen" wrote:
> Mr. Leong,
> Thank you. I didn't think that a database could be attached to a SQL
> Server installation unless it had previously been "detached" with
> sp_detach_db or had been backed up. I have always found it necessary to
> detach the db in order to make a MDF file portable.
> You don't have any reservations about recommending me to go ahead and
> uninstall the trial SQL2000?
> Thanks again.
>
>
>
>
> "Leo Leong" wrote:
> > Hi,
> >
> > i would suggest you to uninstall the SQL Server trial version and purchase a
> > licensed copy.
> > you just need to install the licensed copy of SQL Server.
> > After that, you may need to locate your data file (for your previous database)
> > (For example: C:\program files\Microsoft SQL Server\MSSQL\Data)
> > Then, open your Enterprise Manager, attach the database file.
> >
> > hope this will help.
> >
> > Leo
> >
> > "Paul Deneen" wrote:
> >
> > >
> > > Dear SQL Server experts,
> > >
> > > I'm in a little pickle here, and hope I can avoid trashing many hours of
> > > work. Here's the scenario:
> > > I was running SQL Server 7 on Win2K Server, with several database projects
> > > in development . I installed the 120-day trial version of SQL2000 with the
> > > intention of installing Windows Small Business Server 2003 Premium (which
> > > includes licensed SQL2000) before the end of the trial period. Well, the 120
> > > days came and went, and the SQL2000 installation will, of course, no longer
> > > run. The databases that had been converted to SQL2000 and further developed
> > > were not detached or recently backed up prior to the expiration.
> > >
> > > I fear that just installing the new OS with SQL2000 may result in the
> > > permanent loss of the work since last backup. If there's a way to
> > > re-activate the existing SQL2000 installation, hopefully without purchasing
> > > the standard stand-alone SQL2000, my work may be saved. Any recommendations
> > > for a course of action would be appreciated.
> > >
> > > Thank you.
> > >
> > >
> > >|||It is correct that you are not guaranteed to be able to attach if you don't detach first. Books
Online also states this explicitly. In most cases it will work, but we regularly see posts here from
people where it doesn't work. To play safe, also do backup of those databases, so you then have an
option to restore, if attach doesn't work.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul Deneen" <PaulDeneen@.discussions.microsoft.com> wrote in message
news:858AD928-3B01-4B56-BB31-4B06E270D41E@.microsoft.com...
> Mr. Leong,
> Thank you. I didn't think that a database could be attached to a SQL
> Server installation unless it had previously been "detached" with
> sp_detach_db or had been backed up. I have always found it necessary to
> detach the db in order to make a MDF file portable.
> You don't have any reservations about recommending me to go ahead and
> uninstall the trial SQL2000?
> Thanks again.
>
>
>
>
> "Leo Leong" wrote:
>> Hi,
>> i would suggest you to uninstall the SQL Server trial version and purchase a
>> licensed copy.
>> you just need to install the licensed copy of SQL Server.
>> After that, you may need to locate your data file (for your previous database)
>> (For example: C:\program files\Microsoft SQL Server\MSSQL\Data)
>> Then, open your Enterprise Manager, attach the database file.
>> hope this will help.
>> Leo
>> "Paul Deneen" wrote:
>> >
>> > Dear SQL Server experts,
>> >
>> > I'm in a little pickle here, and hope I can avoid trashing many hours of
>> > work. Here's the scenario:
>> > I was running SQL Server 7 on Win2K Server, with several database projects
>> > in development . I installed the 120-day trial version of SQL2000 with the
>> > intention of installing Windows Small Business Server 2003 Premium (which
>> > includes licensed SQL2000) before the end of the trial period. Well, the 120
>> > days came and went, and the SQL2000 installation will, of course, no longer
>> > run. The databases that had been converted to SQL2000 and further developed
>> > were not detached or recently backed up prior to the expiration.
>> >
>> > I fear that just installing the new OS with SQL2000 may result in the
>> > permanent loss of the work since last backup. If there's a way to
>> > re-activate the existing SQL2000 installation, hopefully without purchasing
>> > the standard stand-alone SQL2000, my work may be saved. Any recommendations
>> > for a course of action would be appreciated.
>> >
>> > Thank you.
>> >
>> >
>> >|||Thank you Mr. Karaszi and Mr. Leong,
I'll have to uninstall SQL2000 and hope for the best on re-attaching the DB,
since I can't backup using the expired trial installation.
Again, thank you for your advice.
-Paul
"Tibor Karaszi" wrote:
> It is correct that you are not guaranteed to be able to attach if you don't detach first. Books
> Online also states this explicitly. In most cases it will work, but we regularly see posts here from
> people where it doesn't work. To play safe, also do backup of those databases, so you then have an
> option to restore, if attach doesn't work.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Paul Deneen" <PaulDeneen@.discussions.microsoft.com> wrote in message
> news:858AD928-3B01-4B56-BB31-4B06E270D41E@.microsoft.com...
> > Mr. Leong,
> >
> > Thank you. I didn't think that a database could be attached to a SQL
> > Server installation unless it had previously been "detached" with
> > sp_detach_db or had been backed up. I have always found it necessary to
> > detach the db in order to make a MDF file portable.
> >
> > You don't have any reservations about recommending me to go ahead and
> > uninstall the trial SQL2000?
> >
> > Thanks again.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > "Leo Leong" wrote:
> >
> >> Hi,
> >>
> >> i would suggest you to uninstall the SQL Server trial version and purchase a
> >> licensed copy.
> >> you just need to install the licensed copy of SQL Server.
> >> After that, you may need to locate your data file (for your previous database)
> >> (For example: C:\program files\Microsoft SQL Server\MSSQL\Data)
> >> Then, open your Enterprise Manager, attach the database file.
> >>
> >> hope this will help.
> >>
> >> Leo
> >>
> >> "Paul Deneen" wrote:
> >>
> >> >
> >> > Dear SQL Server experts,
> >> >
> >> > I'm in a little pickle here, and hope I can avoid trashing many hours of
> >> > work. Here's the scenario:
> >> > I was running SQL Server 7 on Win2K Server, with several database projects
> >> > in development . I installed the 120-day trial version of SQL2000 with the
> >> > intention of installing Windows Small Business Server 2003 Premium (which
> >> > includes licensed SQL2000) before the end of the trial period. Well, the 120
> >> > days came and went, and the SQL2000 installation will, of course, no longer
> >> > run. The databases that had been converted to SQL2000 and further developed
> >> > were not detached or recently backed up prior to the expiration.
> >> >
> >> > I fear that just installing the new OS with SQL2000 may result in the
> >> > permanent loss of the work since last backup. If there's a way to
> >> > re-activate the existing SQL2000 installation, hopefully without purchasing
> >> > the standard stand-alone SQL2000, my work may be saved. Any recommendations
> >> > for a course of action would be appreciated.
> >> >
> >> > Thank you.
> >> >
> >> >
> >> >
>

recovering database from expired trial version

Recovering (local) server and Restoring a Dabase from a clients backup

Hi all,
I'm running sql server 2000.
I've a client who has given me a large database to develope against.
I don't have a (local) server anymore. Can't remember why.
Whats the easiest way to recover (local) - I'm happy to reinstall and start
from a fresh (local).
Also, it looks as though the client has backed up their db.
Am I able to restore to my (local) from their backup?
Thanks,
baz
Yes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>
|||Yes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>
|||Hi Greg,
Thanks for the quick reply.
Thats great news.
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> start
>
|||Hi Greg,
Thanks for the quick reply.
Thats great news.
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> start
>
|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to[vbcol=seagreen]
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
development[vbcol=seagreen]
the
> ----
> --
> ----
> --
>
|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to[vbcol=seagreen]
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
development[vbcol=seagreen]
the
> ----
> --
> ----
> --
>
|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
able[vbcol=seagreen]
> to
you[vbcol=seagreen]
> development
backup.[vbcol=seagreen]
> the
> ----
> ----
and
>
|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
able[vbcol=seagreen]
> to
you[vbcol=seagreen]
> development
backup.[vbcol=seagreen]
> the
> ----
> ----
and
>
|||Hi Peter,
Thanks for the reply.
You have to have a database already setup on your server to restore to.
So my database was only 1 k .
Ten after the failed attempt it is was 750megs.
Had another look thru google.
Looks like some others were having the same prob.
Theirs turned out to be a severely defragmented hard drive.
I've had a look thru mine with DiskKeeper.
Mine is also severely defragmented as well.
I've been defraggin all day but I can't get DiskKeeper to continue defraggin
on its own
I have to keep starting it and it only defrage 50 frags at a time? Who
knows ...
I'll update a followup when I have some news...

Recovering (local) server and Restoring a Dabase from a clients backup

Hi all,
I'm running sql server 2000.
I've a client who has given me a large database to develope against.
I don't have a (local) server anymore. Can't remember why.
Whats the easiest way to recover (local) - I'm happy to reinstall and start
from a fresh (local).
Also, it looks as though the client has backed up their db.
Am I able to restore to my (local) from their backup?
Thanks,
bazYes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>|||Hi Greg,
Thanks for the quick reply.
Thats great news.
--
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > Hi all,
> >
> > I'm running sql server 2000.
> >
> > I've a client who has given me a large database to develope against.
> >
> > I don't have a (local) server anymore. Can't remember why.
> >
> > Whats the easiest way to recover (local) - I'm happy to reinstall and
> start
> > from a fresh (local).
> >
> > Also, it looks as though the client has backed up their db.
> > Am I able to restore to my (local) from their backup?
> >
> > Thanks,
> > baz
> >
> >
> >
> >
>|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > Yes you can restore it. You don't need to restore it locally unless you
> > want to. I would just place the backup some place where your
development
> > server can see it, and then use EM to restore from the database backup.
> > Make sure you type in the name of the database you want to create from
the
> > restore, so you don't overlay some other database.
> > --
> >
> ----
> --
> ----
> --
> > --
> >
> > Need SQL Server Examples check out my website at
> > http://www.geocities.com/sqlserverexamples
> > "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> > news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > > Hi all,
> > >
> > > I'm running sql server 2000.
> > >
> > > I've a client who has given me a large database to develope against.
> > >
> > > I don't have a (local) server anymore. Can't remember why.
> > >
> > > Whats the easiest way to recover (local) - I'm happy to reinstall and
> > start
> > > from a fresh (local).
> > >
> > > Also, it looks as though the client has backed up their db.
> > > Am I able to restore to my (local) from their backup?
> > >
> > > Thanks,
> > > baz
> > >
> > >
> > >
> > >
> >
> >
>|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> > Hi Greg,
> >
> > Thanks for the quick reply.
> >
> > Thats great news.
> >
> > --
> > I'm trying to imulate the client setup as closely as possible.
> > I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> > And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> >
> > So, I do want a (local) server.
> >
> > Anyone have any ideas on how to reinstall or recover the (local) server?
> > I reinstalled sql server last week but the (local) didn't re-appear.
> >
> >
> > And it looks like I have to have a database name already there to be
able
> to
> > recover to it.
> >
> > Any suggestions?
> >
> >
> > "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> > news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > Yes you can restore it. You don't need to restore it locally unless
you
> > > want to. I would just place the backup some place where your
> development
> > > server can see it, and then use EM to restore from the database
backup.
> > > Make sure you type in the name of the database you want to create from
> the
> > > restore, so you don't overlay some other database.
> > > --
> > >
> >
> ----
> > --
> >
> ----
> > --
> > > --
> > >
> > > Need SQL Server Examples check out my website at
> > > http://www.geocities.com/sqlserverexamples
> > > "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> > > news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > > > Hi all,
> > > >
> > > > I'm running sql server 2000.
> > > >
> > > > I've a client who has given me a large database to develope against.
> > > >
> > > > I don't have a (local) server anymore. Can't remember why.
> > > >
> > > > Whats the easiest way to recover (local) - I'm happy to reinstall
and
> > > start
> > > > from a fresh (local).
> > > >
> > > > Also, it looks as though the client has backed up their db.
> > > > Am I able to restore to my (local) from their backup?
> > > >
> > > > Thanks,
> > > > baz
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Hi Peter,
Thanks for the reply.
You have to have a database already setup on your server to restore to.
So my database was only 1 k .
Ten after the failed attempt it is was 750megs.
--
Had another look thru google.
Looks like some others were having the same prob.
Theirs turned out to be a severely defragmented hard drive.
I've had a look thru mine with DiskKeeper.
Mine is also severely defragmented as well.
I've been defraggin all day but I can't get DiskKeeper to continue defraggin
on its own
I have to keep starting it and it only defrage 50 frags at a time? Who
knows ...
I'll update a followup when I have some news...|||Ok I've done it.
DiskKeeper wouldn't defrag enought to make a difference so I had to move my
focus to C: drive.
Still no luck.
I found an older version of w2k on c: drive and removed it.
Defraged with heaps better oucome with diskkeeper.
C: drive then had 4.5 gig free space
Moved backup to C: drive (750 meg)
and created new table on C: drive 1 k - (3.7 gig free on c: drive)
Restored successfully.
now have 3 gig free space
Could have been just the free space restrictions.
Difference between 3.1 failure and 4.5 success.
Anyone know the formula?
Perhaps 3gig / .75 gig failure = 4 times
and 4.5 gig / .75 gig success = 6 times
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> Hi Peter,
> Thanks for the reply.
> You have to have a database already setup on your server to restore
to.
> So my database was only 1 k .
> Ten after the failed attempt it is was 750megs.
> --
>
> Had another look thru google.
> Looks like some others were having the same prob.
> Theirs turned out to be a severely defragmented hard drive.
> I've had a look thru mine with DiskKeeper.
> Mine is also severely defragmented as well.
> I've been defraggin all day but I can't get DiskKeeper to continue
defraggin
> on its own
> I have to keep starting it and it only defrage 50 frags at a time? Who
> knows ...
> I'll update a followup when I have some news...
>|||Don't know if there is such a formula, but it's sure something to keep in
mind. Thx for the update.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23ODumxuXEHA.3944@.tk2msftngp13.phx.gbl...
> Ok I've done it.
> DiskKeeper wouldn't defrag enought to make a difference so I had to move
my
> focus to C: drive.
> Still no luck.
> I found an older version of w2k on c: drive and removed it.
> Defraged with heaps better oucome with diskkeeper.
> C: drive then had 4.5 gig free space
> Moved backup to C: drive (750 meg)
> and created new table on C: drive 1 k - (3.7 gig free on c: drive)
> Restored successfully.
> now have 3 gig free space
> Could have been just the free space restrictions.
> Difference between 3.1 failure and 4.5 success.
> Anyone know the formula?
> Perhaps 3gig / .75 gig failure = 4 times
> and 4.5 gig / .75 gig success = 6 times
> Thanks,
> baz
>
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> > Hi Peter,
> > Thanks for the reply.
> >
> > You have to have a database already setup on your server to restore
> to.
> >
> > So my database was only 1 k .
> > Ten after the failed attempt it is was 750megs.
> >
> > --
> >
> >
> > Had another look thru google.
> >
> > Looks like some others were having the same prob.
> >
> > Theirs turned out to be a severely defragmented hard drive.
> >
> > I've had a look thru mine with DiskKeeper.
> >
> > Mine is also severely defragmented as well.
> >
> > I've been defraggin all day but I can't get DiskKeeper to continue
> defraggin
> > on its own
> > I have to keep starting it and it only defrage 50 frags at a time? Who
> > knows ...
> >
> > I'll update a followup when I have some news...
> >
> >
>

Recovering (local) server and Restoring a Dabase from a clients backup

Monday, March 12, 2012

Recover db after disaster test

After doing an disaster recovery test the sql services aren't running.
When i open the enterprise manager the instance is there but no databases.
All databases are recovered from tape
How can i solve this in proper way?
THX
Are you at least able to see the databases from Query Analyzer? If so, may
be it is a client side issue, and can be resolved by reinstalling client
tools. Any errors in the SQL Server error logs?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
news:139075EF-6815-4A92-A243-D942E4537AA9@.microsoft.com...
After doing an disaster recovery test the sql services aren't running.
When i open the enterprise manager the instance is there but no databases.
All databases are recovered from tape
How can i solve this in proper way?
THX
|||No, in the query analyzer i can only see the instance, no databases.
There if got an error message that he couldn't find sql server services.
So now i'm trying to reinstall the sql server.
"Narayana Vyas Kondreddi" wrote:

> Are you at least able to see the databases from Query Analyzer? If so, may
> be it is a client side issue, and can be resolved by reinstalling client
> tools. Any errors in the SQL Server error logs?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
> news:139075EF-6815-4A92-A243-D942E4537AA9@.microsoft.com...
> After doing an disaster recovery test the sql services aren't running.
> When i open the enterprise manager the instance is there but no databases.
> All databases are recovered from tape
> How can i solve this in proper way?
> THX
>
>
|||Hi,
From Control panel services, see MSSQL Server server is running or not, If
the service is stopped mode, start the service and see if you can see
the databases.
Thanks
Hari
SQL Server MVP
"SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
news:CDD197DF-BC3B-4043-A4DB-E9D0D0969E67@.microsoft.com...[vbcol=seagreen]
> No, in the query analyzer i can only see the instance, no databases.
> There if got an error message that he couldn't find sql server services.
> So now i'm trying to reinstall the sql server.
> "Narayana Vyas Kondreddi" wrote:
may[vbcol=seagreen]
client[vbcol=seagreen]
databases.[vbcol=seagreen]

Recover db after disaster test

After doing an disaster recovery test the sql services aren't running.
When i open the enterprise manager the instance is there but no databases.
All databases are recovered from tape
How can i solve this in proper way?
THXAre you at least able to see the databases from Query Analyzer? If so, may
be it is a client side issue, and can be resolved by reinstalling client
tools. Any errors in the SQL Server error logs?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
news:139075EF-6815-4A92-A243-D942E4537AA9@.microsoft.com...
After doing an disaster recovery test the sql services aren't running.
When i open the enterprise manager the instance is there but no databases.
All databases are recovered from tape
How can i solve this in proper way?
THX|||No, in the query analyzer i can only see the instance, no databases.
There if got an error message that he couldn't find sql server services.
So now i'm trying to reinstall the sql server.
"Narayana Vyas Kondreddi" wrote:

> Are you at least able to see the databases from Query Analyzer? If so, may
> be it is a client side issue, and can be resolved by reinstalling client
> tools. Any errors in the SQL Server error logs?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
> news:139075EF-6815-4A92-A243-D942E4537AA9@.microsoft.com...
> After doing an disaster recovery test the sql services aren't running.
> When i open the enterprise manager the instance is there but no databases.
> All databases are recovered from tape
> How can i solve this in proper way?
> THX
>
>|||Hi,
From Control panel services, see MSSQL Server server is running or not, If
the service is stopped mode, start the service and see if you can see
the databases.
Thanks
Hari
SQL Server MVP
"SQL_dummy" <SQLdummy@.discussions.microsoft.com> wrote in message
news:CDD197DF-BC3B-4043-A4DB-E9D0D0969E67@.microsoft.com...[vbcol=seagreen]
> No, in the query analyzer i can only see the instance, no databases.
> There if got an error message that he couldn't find sql server services.
> So now i'm trying to reinstall the sql server.
> "Narayana Vyas Kondreddi" wrote:
>
may[vbcol=seagreen]
client[vbcol=seagreen]
databases.[vbcol=seagreen]

Recover database with multiple filegroups?

Hi,
I'm running SQL2000 Standard on W2K Server.
I have a large database that spreads multiple physical drives and file
groups. The database failed earlier today because one of the filegroups is
bad. This filegroup is located on a bad drive and the database is now in
(suspect) mode, complaining about torn page I/O error.
I'm wondering if it's possible to DELETE this one filegroup from the
database and bring the database back online with other remaining filegroups.
Because this filegroup is bad and is causing the entire database to be in
Suspect Mode. Or is it possible to re-create a new database by attaching all
good filegroups back?
What are my options for bringing this database back online without having to
trash all the data and reload them? It'd be nice if I only lose this one
filegroup.
Thanks!
HHHi
If I understood you correctly you need to use DBCC SHRINKFILE with EMPTYFILE
argument.
For more details please refer to BOL.
"Hung Huynh" <hungh@.wi.rr.com> wrote in message
news:er8g2TSjDHA.360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm running SQL2000 Standard on W2K Server.
> I have a large database that spreads multiple physical drives and file
> groups. The database failed earlier today because one of the filegroups is
> bad. This filegroup is located on a bad drive and the database is now in
> (suspect) mode, complaining about torn page I/O error.
> I'm wondering if it's possible to DELETE this one filegroup from the
> database and bring the database back online with other remaining
filegroups.
> Because this filegroup is bad and is causing the entire database to be in
> Suspect Mode. Or is it possible to re-create a new database by attaching
all
> good filegroups back?
> What are my options for bringing this database back online without having
to
> trash all the data and reload them? It'd be nice if I only lose this one
> filegroup.
> Thanks!
> HH
>|||No. The database is not functional right now. It's in Suspect Mode and need
to be restored/recovered.
Thanks!
HH
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ufLhsQWjDHA.2652@.TK2MSFTNGP09.phx.gbl...
> Hi
> If I understood you correctly you need to use DBCC SHRINKFILE with
EMPTYFILE
> argument.
> For more details please refer to BOL.
>
>
> "Hung Huynh" <hungh@.wi.rr.com> wrote in message
> news:er8g2TSjDHA.360@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > I'm running SQL2000 Standard on W2K Server.
> >
> > I have a large database that spreads multiple physical drives and file
> > groups. The database failed earlier today because one of the filegroups
is
> > bad. This filegroup is located on a bad drive and the database is now in
> > (suspect) mode, complaining about torn page I/O error.
> >
> > I'm wondering if it's possible to DELETE this one filegroup from the
> > database and bring the database back online with other remaining
> filegroups.
> > Because this filegroup is bad and is causing the entire database to be
in
> > Suspect Mode. Or is it possible to re-create a new database by attaching
> all
> > good filegroups back?
> >
> > What are my options for bringing this database back online without
having
> to
> > trash all the data and reload them? It'd be nice if I only lose this one
> > filegroup.
> >
> > Thanks!
> >
> > HH
> >
> >
>

Friday, March 9, 2012

Recover data from Tables Sql2000

Good Morning,
We have a Win2003 server with SQL2000 running on it. We have an Access Order
Entry application front end with the back end on a database. I was updating
some product pricing in our database and I accidentally DELETED about 360
products. I imported a table with new pricing, and I was updating the prices
in our database with the new prices from an excel spreadsheet.
What is the fastest way I can get back those products? Can I do a roll back
with the trans. log?
Or should I use a backup copy of the database? My automatic maintenance runs
twice a week, so I have backup of the database and logs. But I don't want to
restore the whole database, maybe just one table in the database. Thanks!
Merry Christmas!
Anthony...Although you can't restore a single table, you can restore the entire
database to a different database name and apply your log backups, if needed.
This will allow you to extract the lost data for insertion into your live
database.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Anthony Smith" <anthony@.peconet.com> wrote in message
news:upQJhAP6EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Good Morning,
> We have a Win2003 server with SQL2000 running on it. We have an Access
> Order
> Entry application front end with the back end on a database. I was
> updating
> some product pricing in our database and I accidentally DELETED about 360
> products. I imported a table with new pricing, and I was updating the
> prices
> in our database with the new prices from an excel spreadsheet.
> What is the fastest way I can get back those products? Can I do a roll
> back
> with the trans. log?
> Or should I use a backup copy of the database? My automatic maintenance
> runs
> twice a week, so I have backup of the database and logs. But I don't want
> to
> restore the whole database, maybe just one table in the database. Thanks!
> Merry Christmas!
> Anthony...
>
>|||Thanks for your help. I did it and it work. I'm a SQL novice so I haven't
done much with SQL logs other than back them up.
Have a Merry Christmas!
Anthony...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OHjywKP6EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Although you can't restore a single table, you can restore the entire
> database to a different database name and apply your log backups, if
> needed. This will allow you to extract the lost data for insertion into
> your live database.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Anthony Smith" <anthony@.peconet.com> wrote in message
> news:upQJhAP6EHA.2016@.TK2MSFTNGP15.phx.gbl...
>> Good Morning,
>> We have a Win2003 server with SQL2000 running on it. We have an Access
>> Order
>> Entry application front end with the back end on a database. I was
>> updating
>> some product pricing in our database and I accidentally DELETED about 360
>> products. I imported a table with new pricing, and I was updating the
>> prices
>> in our database with the new prices from an excel spreadsheet.
>> What is the fastest way I can get back those products? Can I do a roll
>> back
>> with the trans. log?
>> Or should I use a backup copy of the database? My automatic maintenance
>> runs
>> twice a week, so I have backup of the database and logs. But I don't want
>> to
>> restore the whole database, maybe just one table in the database.
>> Thanks!
>> Merry Christmas!
>> Anthony...
>>
>|||That's better than most novices; at least you know they exist and have the
sense to back them up.
Sincerely,
Anthony Thomas
"Anthony Smith" <anthony@.peconet.com> wrote in message
news:eMsKduP6EHA.1596@.tk2msftngp13.phx.gbl...
Thanks for your help. I did it and it work. I'm a SQL novice so I haven't
done much with SQL logs other than back them up.
Have a Merry Christmas!
Anthony...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OHjywKP6EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Although you can't restore a single table, you can restore the entire
> database to a different database name and apply your log backups, if
> needed. This will allow you to extract the lost data for insertion into
> your live database.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Anthony Smith" <anthony@.peconet.com> wrote in message
> news:upQJhAP6EHA.2016@.TK2MSFTNGP15.phx.gbl...
>> Good Morning,
>> We have a Win2003 server with SQL2000 running on it. We have an Access
>> Order
>> Entry application front end with the back end on a database. I was
>> updating
>> some product pricing in our database and I accidentally DELETED about 360
>> products. I imported a table with new pricing, and I was updating the
>> prices
>> in our database with the new prices from an excel spreadsheet.
>> What is the fastest way I can get back those products? Can I do a roll
>> back
>> with the trans. log?
>> Or should I use a backup copy of the database? My automatic maintenance
>> runs
>> twice a week, so I have backup of the database and logs. But I don't want
>> to
>> restore the whole database, maybe just one table in the database.
>> Thanks!
>> Merry Christmas!
>> Anthony...
>>
>

Recover data from corrupt DB

Hi all:
I have MSCRM running in a VPC setup, so since I had 4 backup copies of the
VHD files, I never backed up the DBs themselves. Now for some reason all of
the images have an error in the MSCRM Metabase database, and I cannot
recover it. I tried this:
1. alter database Adventure_Works_Cycle_METABASE set emergency
2. sp_dboption Adventure_Works_Cycle_METABASE, single, true
3. dbcc checkdb (Adventure_Works_Cycle_METABASE, repair_allow_data_loss)
4. sp_dboption Adventure_Works_Cycle_METABASE, single, false
Which got the DB back online, but it dumped a bunch of necessary data and
broke MSCRM.
Can anyone make any suggestions as to how I can save the data? The metabase
tracks customizations to MSCRM, so if I lose it I'll lose all of my work.
Thanks in advance for any and all help.
John.
This message sent from Windows Vista Ultimate
http://mscrmguy.blogspot.com/
John
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
"John" <jstraumann@.nospam.hotmail.com> wrote in message
news:929ACB25-076E-4714-AC77-144F44FD319B@.microsoft.com...
> Hi all:
> I have MSCRM running in a VPC setup, so since I had 4 backup copies of the
> VHD files, I never backed up the DBs themselves. Now for some reason all
> of the images have an error in the MSCRM Metabase database, and I cannot
> recover it. I tried this:
> 1. alter database Adventure_Works_Cycle_METABASE set emergency
> 2. sp_dboption Adventure_Works_Cycle_METABASE, single, true
> 3. dbcc checkdb (Adventure_Works_Cycle_METABASE, repair_allow_data_loss)
> 4. sp_dboption Adventure_Works_Cycle_METABASE, single, false
> Which got the DB back online, but it dumped a bunch of necessary data and
> broke MSCRM.
> Can anyone make any suggestions as to how I can save the data? The
> metabase tracks customizations to MSCRM, so if I lose it I'll lose all of
> my work.
> Thanks in advance for any and all help.
> John.
> --
> This message sent from Windows Vista Ultimate
> http://mscrmguy.blogspot.com/
>
|||Thanks but those steps only work if the DB is backed up.
This message sent from Windows Vista Ultimate
http://mscrmguy.blogspot.com/
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23039dpcGHHA.1188@.TK2MSFTNGP06.phx.gbl...
> John
> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>
> "John" <jstraumann@.nospam.hotmail.com> wrote in message
> news:929ACB25-076E-4714-AC77-144F44FD319B@.microsoft.com...
>

Friday, March 23, 2012

recovering from a clustered node failure

recovering from a clustered node failure

Wednesday, March 21, 2012

recovering database from expired trial version

recovering database from expired trial version

recovering database from expired trial version

Recovering (local) server and Restoring a Dabase from a clients backup

Recovering (local) server and Restoring a Dabase from a clients backup

Recovering (local) server and Restoring a Dabase from a clients backup

Monday, March 12, 2012

Recover db after disaster test

Recover db after disaster test

Recover database with multiple filegroups?

Friday, March 9, 2012

Recover data from Tables Sql2000

Recover data from Tables Sql2000

Recover data from corrupt DB

Record Locks

Blog Archive

About Me