Hi all !
I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
2000(SP3). It takes a few minutes to restore it on another box which has
enough resurses, but when I tried to do the same on a box that is a bit old
and not so powerfull I just couldn't wait until it's done, - i canceled
restore operation. As a workaround I detached DB file and then attached them
on that box. But I'm still wondering is there another way to restore DB, may
be group by group or ...?
Thanks a lot in advance,
Alex
Backup and restore
and
sp_detach_db and sp_attach_db
are the best options
You could also try using DTS, but that would probably involve much more
effort on your part.
Keith
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>
|||Did you restore the database on the 'old box' when the database was not yet
created? If this was the first time, the 5 Gig file needs to be created
first before the restore can start, and depending on the speed of your disk
controllers, this might take some time. When you subsequently restore the
database again, don't delete the old database first.
Since you already have the database on the old box, try restoring using the
normal way, and see if it still takes as long. And by any chance, are you
using compressed folders?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>
|||Yes, I created DB before restoring with two file groups 2 G each and log
file. And I wasn't using compressed folder. My guess is maybe I wasn't
patient enough although I waited for about half an hour to let it finish.
But that 'old box' is really slow and that could be the case. I'll give it
another try and be more patien this time.
Thank you,
Alex
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:u2AMSofbEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Did you restore the database on the 'old box' when the database was not
yet
> created? If this was the first time, the 5 Gig file needs to be created
> first before the restore can start, and depending on the speed of your
disk
> controllers, this might take some time. When you subsequently restore the
> database again, don't delete the old database first.
> Since you already have the database on the old box, try restoring using
the[vbcol=seagreen]
> normal way, and see if it still takes as long. And by any chance, are you
> using compressed folders?
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Try MiniSQLBackup
>
> "Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
> news:10fo5ivqif63e54@.corp.supernews.com...
has
> old
> them
> may
>
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Friday, March 30, 2012
long running RESTORE
Hi all !
I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
2000(SP3). It takes a few minutes to restore it on another box which has
enough resurses, but when I tried to do the same on a box that is a bit old
and not so powerfull I just couldn't wait until it's done, - i canceled
restore operation. As a workaround I detached DB file and then attached them
on that box. But I'm still wondering is there another way to restore DB, may
be group by group or ...?
--
Thanks a lot in advance,
AlexBackup and restore
and
sp_detach_db and sp_attach_db
are the best options
You could also try using DTS, but that would probably involve much more
effort on your part.
Keith
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Did you restore the database on the 'old box' when the database was not yet
created? If this was the first time, the 5 Gig file needs to be created
first before the restore can start, and depending on the speed of your disk
controllers, this might take some time. When you subsequently restore the
database again, don't delete the old database first.
Since you already have the database on the old box, try restoring using the
normal way, and see if it still takes as long. And by any chance, are you
using compressed folders?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Yes, I created DB before restoring with two file groups 2 G each and log
file. And I wasn't using compressed folder. My guess is maybe I wasn't
patient enough although I waited for about half an hour to let it finish.
But that 'old box' is really slow and that could be the case. I'll give it
another try and be more patien this time.
Thank you,
Alex
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:u2AMSofbEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Did you restore the database on the 'old box' when the database was not
yet
> created? If this was the first time, the 5 Gig file needs to be created
> first before the restore can start, and depending on the speed of your
disk
> controllers, this might take some time. When you subsequently restore the
> database again, don't delete the old database first.
> Since you already have the database on the old box, try restoring using
the
> normal way, and see if it still takes as long. And by any chance, are you
> using compressed folders?
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Try MiniSQLBackup
>
> "Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
> news:10fo5ivqif63e54@.corp.supernews.com...
has[vbcol=seagreen]
> old
> them
> may
>
I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
2000(SP3). It takes a few minutes to restore it on another box which has
enough resurses, but when I tried to do the same on a box that is a bit old
and not so powerfull I just couldn't wait until it's done, - i canceled
restore operation. As a workaround I detached DB file and then attached them
on that box. But I'm still wondering is there another way to restore DB, may
be group by group or ...?
--
Thanks a lot in advance,
AlexBackup and restore
and
sp_detach_db and sp_attach_db
are the best options
You could also try using DTS, but that would probably involve much more
effort on your part.
Keith
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Did you restore the database on the 'old box' when the database was not yet
created? If this was the first time, the 5 Gig file needs to be created
first before the restore can start, and depending on the speed of your disk
controllers, this might take some time. When you subsequently restore the
database again, don't delete the old database first.
Since you already have the database on the old box, try restoring using the
normal way, and see if it still takes as long. And by any chance, are you
using compressed folders?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Yes, I created DB before restoring with two file groups 2 G each and log
file. And I wasn't using compressed folder. My guess is maybe I wasn't
patient enough although I waited for about half an hour to let it finish.
But that 'old box' is really slow and that could be the case. I'll give it
another try and be more patien this time.
Thank you,
Alex
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:u2AMSofbEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Did you restore the database on the 'old box' when the database was not
yet
> created? If this was the first time, the 5 Gig file needs to be created
> first before the restore can start, and depending on the speed of your
disk
> controllers, this might take some time. When you subsequently restore the
> database again, don't delete the old database first.
> Since you already have the database on the old box, try restoring using
the
> normal way, and see if it still takes as long. And by any chance, are you
> using compressed folders?
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Try MiniSQLBackup
>
> "Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
> news:10fo5ivqif63e54@.corp.supernews.com...
has[vbcol=seagreen]
> old
> them
> may
>
long running RESTORE
Hi all !
I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
2000(SP3). It takes a few minutes to restore it on another box which has
enough resurses, but when I tried to do the same on a box that is a bit old
and not so powerfull I just couldn't wait until it's done, - i canceled
restore operation. As a workaround I detached DB file and then attached them
on that box. But I'm still wondering is there another way to restore DB, may
be group by group or ...?
--
Thanks a lot in advance,
AlexBackup and restore
and
sp_detach_db and sp_attach_db
are the best options
You could also try using DTS, but that would probably involve much more
effort on your part.
--
Keith
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Did you restore the database on the 'old box' when the database was not yet
created? If this was the first time, the 5 Gig file needs to be created
first before the restore can start, and depending on the speed of your disk
controllers, this might take some time. When you subsequently restore the
database again, don't delete the old database first.
Since you already have the database on the old box, try restoring using the
normal way, and see if it still takes as long. And by any chance, are you
using compressed folders?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Yes, I created DB before restoring with two file groups 2 G each and log
file. And I wasn't using compressed folder. My guess is maybe I wasn't
patient enough although I waited for about half an hour to let it finish.
But that 'old box' is really slow and that could be the case. I'll give it
another try and be more patien this time.
--
Thank you,
Alex
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:u2AMSofbEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Did you restore the database on the 'old box' when the database was not
yet
> created? If this was the first time, the 5 Gig file needs to be created
> first before the restore can start, and depending on the speed of your
disk
> controllers, this might take some time. When you subsequently restore the
> database again, don't delete the old database first.
> Since you already have the database on the old box, try restoring using
the
> normal way, and see if it still takes as long. And by any chance, are you
> using compressed folders?
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Try MiniSQLBackup
>
> "Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
> news:10fo5ivqif63e54@.corp.supernews.com...
> > Hi all !
> >
> > I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> > 2000(SP3). It takes a few minutes to restore it on another box which
has
> > enough resurses, but when I tried to do the same on a box that is a bit
> old
> > and not so powerfull I just couldn't wait until it's done, - i canceled
> > restore operation. As a workaround I detached DB file and then attached
> them
> > on that box. But I'm still wondering is there another way to restore DB,
> may
> > be group by group or ...?
> > --
> >
> > Thanks a lot in advance,
> >
> > Alex
> >
> >
>
I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
2000(SP3). It takes a few minutes to restore it on another box which has
enough resurses, but when I tried to do the same on a box that is a bit old
and not so powerfull I just couldn't wait until it's done, - i canceled
restore operation. As a workaround I detached DB file and then attached them
on that box. But I'm still wondering is there another way to restore DB, may
be group by group or ...?
--
Thanks a lot in advance,
AlexBackup and restore
and
sp_detach_db and sp_attach_db
are the best options
You could also try using DTS, but that would probably involve much more
effort on your part.
--
Keith
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Did you restore the database on the 'old box' when the database was not yet
created? If this was the first time, the 5 Gig file needs to be created
first before the restore can start, and depending on the speed of your disk
controllers, this might take some time. When you subsequently restore the
database again, don't delete the old database first.
Since you already have the database on the old box, try restoring using the
normal way, and see if it still takes as long. And by any chance, are you
using compressed folders?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
news:10fo5ivqif63e54@.corp.supernews.com...
> Hi all !
> I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> 2000(SP3). It takes a few minutes to restore it on another box which has
> enough resurses, but when I tried to do the same on a box that is a bit
old
> and not so powerfull I just couldn't wait until it's done, - i canceled
> restore operation. As a workaround I detached DB file and then attached
them
> on that box. But I'm still wondering is there another way to restore DB,
may
> be group by group or ...?
> --
> Thanks a lot in advance,
> Alex
>|||Yes, I created DB before restoring with two file groups 2 G each and log
file. And I wasn't using compressed folder. My guess is maybe I wasn't
patient enough although I waited for about half an hour to let it finish.
But that 'old box' is really slow and that could be the case. I'll give it
another try and be more patien this time.
--
Thank you,
Alex
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:u2AMSofbEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Did you restore the database on the 'old box' when the database was not
yet
> created? If this was the first time, the 5 Gig file needs to be created
> first before the restore can start, and depending on the speed of your
disk
> controllers, this might take some time. When you subsequently restore the
> database again, don't delete the old database first.
> Since you already have the database on the old box, try restoring using
the
> normal way, and see if it still takes as long. And by any chance, are you
> using compressed folders?
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Try MiniSQLBackup
>
> "Alex" <amakarov_removethis_@.healthmetrx.com> wrote in message
> news:10fo5ivqif63e54@.corp.supernews.com...
> > Hi all !
> >
> > I have 5 GB backup file of DB running in SIMPLE recovery mode on SQL
> > 2000(SP3). It takes a few minutes to restore it on another box which
has
> > enough resurses, but when I tried to do the same on a box that is a bit
> old
> > and not so powerfull I just couldn't wait until it's done, - i canceled
> > restore operation. As a workaround I detached DB file and then attached
> them
> > on that box. But I'm still wondering is there another way to restore DB,
> may
> > be group by group or ...?
> > --
> >
> > Thanks a lot in advance,
> >
> > Alex
> >
> >
>
Friday, March 23, 2012
logshipping error
Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0--
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceThis is a multi-part message in MIME format.
--040104080107040407070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
--040104080107040407070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Sounds like the corruption on the primary DB has put the tlog syncs
out of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the
log shipping pair for you using the DB maint wizard.)</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:bijupg@.hotmail.com">bijupg@.hotmail.com</a> wrote:
<blockquote cite="midD73EA24F-DBEA-4E4F-9F4F-797DC31E31FF@.microsoft.com"
type="cite">
<pre wrap="">Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
</pre>
</blockquote>
</body>
</html>
--040104080107040407070908--|||This is a multi-part message in MIME format.
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
--=_NextPart_000_000D_01C56A79.C4EDC0F0--
logshipping error
Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceSounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][O
DBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceSounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][O
DBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
logshipping error
Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:
>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon
Wednesday, March 21, 2012
LogShipping
Hi all I have created a log shipping task in my SQL servers
This Is the server order
Ist Server (Win2003 , SQL 2000 sp3) is the data server let's say
2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
3rd Server (win2000, SQL 2000 sp3) Is the server that accepts the data
(1st & 2nd server is a clucter system )
And the line Connecting 1st & 2nd Server with the 3rd server is 1MB
The problem now is that the SQL Help is awful about logshipping. It explains
nothing!!
I have Create the log shipping but i get en error that the databases are not
sync.
And the FileLoaded and file copped is stack on First_File...trn
And also my databades seemed to be in sync
What Is wrong'
What should I do'
Please HELP!!!
Thanks in advance
DimitrisHi,
I have to correct you on something...there is plenty of
documentation for log shipping!
Try looking at BOL and this link will help. You should
read before implementing.
http://support.microsoft.com/?id=323135
hth
DeeJay
>--Original Message--
>Hi all I have created a log shipping task in my SQL
servers
>This Is the server order
>Ist Server (Win2003 , SQL 2000 sp3) is the data server
let's say
>2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
>3rd Server (win2000, SQL 2000 sp3) Is the server that
accepts the data
>(1st & 2nd server is a clucter system )
>And the line Connecting 1st & 2nd Server with the 3rd
server is 1MB
>The problem now is that the SQL Help is awful about
logshipping. It explains
>nothing!!
>I have Create the log shipping but i get en error that
the databases are not
>sync.
>And the FileLoaded and file copped is stack on
First_File...trn
>And also my databades seemed to be in sync
>What Is wrong'
>What should I do'
>Please HELP!!!
>Thanks in advance
>Dimitris
>
>
>.
>
This Is the server order
Ist Server (Win2003 , SQL 2000 sp3) is the data server let's say
2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
3rd Server (win2000, SQL 2000 sp3) Is the server that accepts the data
(1st & 2nd server is a clucter system )
And the line Connecting 1st & 2nd Server with the 3rd server is 1MB
The problem now is that the SQL Help is awful about logshipping. It explains
nothing!!
I have Create the log shipping but i get en error that the databases are not
sync.
And the FileLoaded and file copped is stack on First_File...trn
And also my databades seemed to be in sync
What Is wrong'
What should I do'
Please HELP!!!
Thanks in advance
DimitrisHi,
I have to correct you on something...there is plenty of
documentation for log shipping!
Try looking at BOL and this link will help. You should
read before implementing.
http://support.microsoft.com/?id=323135
hth
DeeJay
>--Original Message--
>Hi all I have created a log shipping task in my SQL
servers
>This Is the server order
>Ist Server (Win2003 , SQL 2000 sp3) is the data server
let's say
>2nd Server (win2003 , SQL 2000 sp3) Is the monitor server
>3rd Server (win2000, SQL 2000 sp3) Is the server that
accepts the data
>(1st & 2nd server is a clucter system )
>And the line Connecting 1st & 2nd Server with the 3rd
server is 1MB
>The problem now is that the SQL Help is awful about
logshipping. It explains
>nothing!!
>I have Create the log shipping but i get en error that
the databases are not
>sync.
>And the FileLoaded and file copped is stack on
First_File...trn
>And also my databades seemed to be in sync
>What Is wrong'
>What should I do'
>Please HELP!!!
>Thanks in advance
>Dimitris
>
>
>.
>
LOGON TRIGGERS
Are there any plans to enhance LOGON TRIGGERS in Katmai or SP3 for SQL Server 2005?
And I mean by enhancements:
- providing base scripts that can be adapter for specific scenarios like limiting the number of connections
- any interface (like the Windows Server Active Directory Users and Computers Snap-in for managing Logon Hours)
- etc
These is some documentation for basic scripts in the works.
I can update this thread when they can be released.
Thanks,
-Steven Gott
SDE/T
SQL Server
|||Also Books Online states the following:
Important: In addition to enabling the common criteria compliance enabled option, you also must download and run a script that completes configuring SQL Server 2005 SP2 to comply with Common Criteria evaluation assurance level 4 (EAL4+). You can download this script from the Microsoft SQL Server Common Criteria Web site.
But the script is for SP1. What about the script for SP2?
Monday, March 19, 2012
LOGON TRIGGERS
Are there any plans to enhance LOGON TRIGGERS in Katmai or SP3 for SQL Server 2005?
And I mean by enhancements:
- providing base scripts that can be adapter for specific scenarios like limiting the number of connections
- any interface (like the Windows Server Active Directory Users and Computers Snap-in for managing Logon Hours)
- etc
These is some documentation for basic scripts in the works.
I can update this thread when they can be released.
Thanks,
-Steven Gott
SDE/T
SQL Server
|||Also Books Online states the following:
Important: In addition to enabling the common criteria compliance enabled option, you also must download and run a script that completes configuring SQL Server 2005 SP2 to comply with Common Criteria evaluation assurance level 4 (EAL4+). You can download this script from the Microsoft SQL Server Common Criteria Web site.
But the script is for SP1. What about the script for SP2?
LOGON TRIGGERS
Are there any plans to enhance LOGON TRIGGERS in Katmai or SP3 for SQL Server 2005?
And I mean by enhancements:
- providing base scripts that can be adapter for specific scenarios like limiting the number of connections
- any interface (like the Windows Server Active Directory Users and Computers Snap-in for managing Logon Hours)
- etc
These is some documentation for basic scripts in the works.
I can update this thread when they can be released.
Thanks,
-Steven Gott
SDE/T
SQL Server
|||Also Books Online states the following:
Important: In addition to enabling the common criteria compliance enabled option, you also must download and run a script that completes configuring SQL Server 2005 SP2 to comply with Common Criteria evaluation assurance level 4 (EAL4+). You can download this script from the Microsoft SQL Server Common Criteria Web site.
But the script is for SP1. What about the script for SP2?
Friday, February 24, 2012
login probs after restore
sql2k sp3
About once a month Im asked to take a backup from
production and restore it in a development environment.
(these are in the same domain) After the restore, I can
see the users in the db, but those users cant see the db
from tools like Query Analyzer. I have to actually drop/
recreate the users from the db and then reset the perms to
get them going. Not a big deal for me, but there has got
to be a better way? Any ideas?
TIA, ChrisRHi,
Yes, the better way is to execute "sp_change_users_login" procedure from the
restored database.
See the details of sp_change_users_login procedure in books online.
Thanks
Hari
MCDBA
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR|||Chris,
the SID in master.dbo.sysxlogins needs to map to the SID
in yourdb.dbo.sysusers and there is a sp to help you remap
them in a backup/restore scenario:
sp_change_users_login
Full details are in BOL, but this procedure will mean you
can retain the users and permissions.
HTH,
Paul Ibison|||Thanks Paul. Do you know what I use for the WINNT guys?
>--Original Message--
>Chris,
>the SID in master.dbo.sysxlogins needs to map to the SID
>in yourdb.dbo.sysusers and there is a sp to help you
remap
>them in a backup/restore scenario:
>sp_change_users_login
>Full details are in BOL, but this procedure will mean you
>can retain the users and permissions.
>HTH,
>Paul Ibison
>.
>|||Chris,
as far as I understand these should be OK as the SID won't
change as you're still in the same domain. You can use
sp_validatelogins to be sure.
Also, Rand from MS has previously posted up this link for
mapping both types of logins :
http://support.microsoft.com/default.aspx?kbid=298897
Regards,
Paul Ibison|||Also, search KB and read about sp_help_revlogin.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR
About once a month Im asked to take a backup from
production and restore it in a development environment.
(these are in the same domain) After the restore, I can
see the users in the db, but those users cant see the db
from tools like Query Analyzer. I have to actually drop/
recreate the users from the db and then reset the perms to
get them going. Not a big deal for me, but there has got
to be a better way? Any ideas?
TIA, ChrisRHi,
Yes, the better way is to execute "sp_change_users_login" procedure from the
restored database.
See the details of sp_change_users_login procedure in books online.
Thanks
Hari
MCDBA
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR|||Chris,
the SID in master.dbo.sysxlogins needs to map to the SID
in yourdb.dbo.sysusers and there is a sp to help you remap
them in a backup/restore scenario:
sp_change_users_login
Full details are in BOL, but this procedure will mean you
can retain the users and permissions.
HTH,
Paul Ibison|||Thanks Paul. Do you know what I use for the WINNT guys?
>--Original Message--
>Chris,
>the SID in master.dbo.sysxlogins needs to map to the SID
>in yourdb.dbo.sysusers and there is a sp to help you
remap
>them in a backup/restore scenario:
>sp_change_users_login
>Full details are in BOL, but this procedure will mean you
>can retain the users and permissions.
>HTH,
>Paul Ibison
>.
>|||Chris,
as far as I understand these should be OK as the SID won't
change as you're still in the same domain. You can use
sp_validatelogins to be sure.
Also, Rand from MS has previously posted up this link for
mapping both types of logins :
http://support.microsoft.com/default.aspx?kbid=298897
Regards,
Paul Ibison|||Also, search KB and read about sp_help_revlogin.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR
Subscribe to:
Posts (Atom)