Is there a way that one can detach/move a database that is in norecovery or
standby state thats awaiting more T-logs to be applied and then attach/bring
it
back in the same state and continue with T-logs restores ? I know one can
detach a nonrecovered/standby database but while attaching it it recovers
it... and
that what i want to avoid.
Any way to modify some system tables (sysdatabases) to achieve this. Any
help would be much appreciated. Using SQL 2000.Not that I can see. I had a couple of tries at this but I see no documented
way to do it. As you rightly say, FOR ATTACH recovers the database. I guess
you could probably do something with the status but I would not recomend
hacking the system tables.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OPA7f$$cDHA.2416@.TK2MSFTNGP09.phx.gbl...
Is there a way that one can detach/move a database that is in norecovery or
standby state thats awaiting more T-logs to be applied and then attach/bring
it
back in the same state and continue with T-logs restores ? I know one can
detach a nonrecovered/standby database but while attaching it it recovers
it... and
that what i want to avoid.
Any way to modify some system tables (sysdatabases) to achieve this. Any
help would be much appreciated. Using SQL 2000.|||All I would say is that it would probably be unsupported should you
encounter any issues so you're on your own. If this is a production
environment I would strongly recomend against it.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%237mkvdJdDHA.2804@.TK2MSFTNGP11.phx.gbl...
I tried to do this and was successful. It does involve hacking sysdatabases
. But am also hesitant as I am not too sure what the future holds. It works
fine now...But would hate to see some error later down the line
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ucdZNaIdDHA.1128@.tk2msftngp13.phx.gbl...
> Not that I can see. I had a couple of tries at this but I see no
documented
> way to do it. As you rightly say, FOR ATTACH recovers the database. I
guess
> you could probably do something with the status but I would not recomend
> hacking the system tables.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:OPA7f$$cDHA.2416@.TK2MSFTNGP09.phx.gbl...
> Is there a way that one can detach/move a database that is in norecovery
or
> standby state thats awaiting more T-logs to be applied and then
attach/bring
> it
> back in the same state and continue with T-logs restores ? I know one can
> detach a nonrecovered/standby database but while attaching it it recovers
> it... and
> that what i want to avoid.
> Any way to modify some system tables (sysdatabases) to achieve this. Any
> help would be much appreciated. Using SQL 2000.
>
>
Showing posts with label applied. Show all posts
Showing posts with label applied. Show all posts
Wednesday, March 21, 2012
Post SQL 2000 SP4 hotfixes - confused??
Hi,
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
> some other hotfixes which I don't know if they need to be applied as well or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
> > Hi,
> >
> > I'm confused with what hotfixes needs to be applied after installing SQL
> > Server 2000 SP4. One of my server is using AWE so applying hotfix -
899761
> > (FIX: Not all memory is available when AWE is enabled on a computer that
is
> > running a 32-bit version of SQL Server 2000 SP4) makes sense, but there
are
> > some other hotfixes which I don't know if they need to be applied as
well or
> > not. Those hotfixes are:
> >
> > 836651 (FIX: You receive query results that were not expected when you
use
> > both ANSI joins and non-ANSI joins)
> >
> > 826906 (FIX: A query that uses a view that contains a correlated
subquery
> > and an aggregate runs slowly)
> >
> > 887165 (BUG: You may receive an "Access is denied" error message when a
> > query calls an extended stored procedure after you upgrade from SQL
Server
> > 2000 to SQL Server 2000 Service Pack 4)
> >
> > Do I have also apply the above hotfixes as well? If yes, then in what
> > sequence or it doesn't matter?
> >
> > TIA.
> >
> > Regards,
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.
> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
> some other hotfixes which I don't know if they need to be applied as well or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
> > Hi,
> >
> > I'm confused with what hotfixes needs to be applied after installing SQL
> > Server 2000 SP4. One of my server is using AWE so applying hotfix -
899761
> > (FIX: Not all memory is available when AWE is enabled on a computer that
is
> > running a 32-bit version of SQL Server 2000 SP4) makes sense, but there
are
> > some other hotfixes which I don't know if they need to be applied as
well or
> > not. Those hotfixes are:
> >
> > 836651 (FIX: You receive query results that were not expected when you
use
> > both ANSI joins and non-ANSI joins)
> >
> > 826906 (FIX: A query that uses a view that contains a correlated
subquery
> > and an aggregate runs slowly)
> >
> > 887165 (BUG: You may receive an "Access is denied" error message when a
> > query calls an extended stored procedure after you upgrade from SQL
Server
> > 2000 to SQL Server 2000 Service Pack 4)
> >
> > Do I have also apply the above hotfixes as well? If yes, then in what
> > sequence or it doesn't matter?
> >
> > TIA.
> >
> > Regards,
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.
> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan
Tuesday, March 20, 2012
Post SQL 2000 SP4 hotfixes - confused??
Hi,
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that i
s
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there ar
e
> some other hotfixes which I don't know if they need to be applied as well
or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
899761[vbcol=seagreen]
is[vbcol=seagreen]
are[vbcol=seagreen]
well or[vbcol=seagreen]
use[vbcol=seagreen]
subquery[vbcol=seagreen]
Server[vbcol=seagreen]
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.
> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan
I'm confused with what hotfixes needs to be applied after installing SQL
Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
(FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4) makes sense, but there are
some other hotfixes which I don't know if they need to be applied as well or
not. Those hotfixes are:
836651 (FIX: You receive query results that were not expected when you use
both ANSI joins and non-ANSI joins)
826906 (FIX: A query that uses a view that contains a correlated subquery
and an aggregate runs slowly)
887165 (BUG: You may receive an "Access is denied" error message when a
query calls an extended stored procedure after you upgrade from SQL Server
2000 to SQL Server 2000 Service Pack 4)
Do I have also apply the above hotfixes as well? If yes, then in what
sequence or it doesn't matter?
TIA.
Regards,Rob wrote:
> Hi,
> I'm confused with what hotfixes needs to be applied after installing SQL
> Server 2000 SP4. One of my server is using AWE so applying hotfix - 899761
> (FIX: Not all memory is available when AWE is enabled on a computer that i
s
> running a 32-bit version of SQL Server 2000 SP4) makes sense, but there ar
e
> some other hotfixes which I don't know if they need to be applied as well
or
> not. Those hotfixes are:
> 836651 (FIX: You receive query results that were not expected when you use
> both ANSI joins and non-ANSI joins)
> 826906 (FIX: A query that uses a view that contains a correlated subquery
> and an aggregate runs slowly)
> 887165 (BUG: You may receive an "Access is denied" error message when a
> query calls an extended stored procedure after you upgrade from SQL Server
> 2000 to SQL Server 2000 Service Pack 4)
> Do I have also apply the above hotfixes as well? If yes, then in what
> sequence or it doesn't matter?
> TIA.
> Regards,
In general, you should apply any patch that is available. Always apply
them to a development or test server first, let them cook there for a
period of time, then deploy to production. Better to apply them *at
your convenience* than when the place is on fire...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:u3u7XV0qGHA.3248@.TK2MSFTNGP04.phx.gbl...
> Rob wrote:
899761[vbcol=seagreen]
is[vbcol=seagreen]
are[vbcol=seagreen]
well or[vbcol=seagreen]
use[vbcol=seagreen]
subquery[vbcol=seagreen]
Server[vbcol=seagreen]
> In general, you should apply any patch that is available.
I will dispute that. And in general Microsoft suggests that you do NOT
apply hot patches unless the fix applies to you. They do not have the full
amount of testing that a service patch has.
> Always apply
> them to a development or test server first, let them cook there for a
> period of time, then deploy to production. Better to apply them *at
> your convenience* than when the place is on fire...
If you do have to apply them, I do agree with this.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hello, Rob
Hotfixes for SQL Server are cummulative (for the same service pack
level), so if you install a later hotfix there is no need to install
the previous hotfixes.
In particular, the first two KB articles you mentioned (836651 and
826906) correspond to the same post-SP4 hotfix (8.00.2145). However,
the post-SP3 versions of the hotfixes are different (8.00.913 and
8.00.850, respectively), but since those post-SP3 hotfixes were not
included in SP4, another post-SP4 hotfix (i.e. 8.00.2145) was made.
This post-SP4 hotfix was not publicily available, so if you are
affected by those problems, it is recommended to install the
cummulative hotfix build 2187, downloadable from KB article 916287.
This post-SP4 hotfix contains all the post-SP3 hotfixes that were not
included in SP4, the AWE hotfix (and possibly some other hotfixes).
Normally, Microsoft recommends that you do not install any particular
hotfix unless you are affected by that specific problem. However, for
cummulative hotfix build 2187 they did not issue this recommendation,
which makes me believe that this hotfix was more thoroughly tested.
Regarding the last KB article you mentioned, there is no hotfix for
that problem. The KB article 887165 only documents the problem and
provides workarounds.
Razvan
Monday, March 12, 2012
Possible to undo a restore operation?
I just restored a db from its full backup and then applied its diff backup
and a log backup. Now I need to know how the db looked like before the log
backup was applied. Is it possible to undo the restore from the log backup?
Thanks,
BingNope. You will have to redo the restore and stop one step earlier.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bing" <bing@.discussions.microsoft.com> wrote in message
news:F9861F7C-1D50-40C7-8B83-3ECCDC838AD8@.microsoft.com...
> I just restored a db from its full backup and then applied its diff backup
> and a log backup. Now I need to know how the db looked like before the
log
> backup was applied. Is it possible to undo the restore from the log
backup?
> Thanks,
> Bing
and a log backup. Now I need to know how the db looked like before the log
backup was applied. Is it possible to undo the restore from the log backup?
Thanks,
BingNope. You will have to redo the restore and stop one step earlier.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bing" <bing@.discussions.microsoft.com> wrote in message
news:F9861F7C-1D50-40C7-8B83-3ECCDC838AD8@.microsoft.com...
> I just restored a db from its full backup and then applied its diff backup
> and a log backup. Now I need to know how the db looked like before the
log
> backup was applied. Is it possible to undo the restore from the log
backup?
> Thanks,
> Bing
Possible to undo a restore operation?
I just restored a db from its full backup and then applied its diff backup
and a log backup. Now I need to know how the db looked like before the log
backup was applied. Is it possible to undo the restore from the log backup?
Thanks,
Bing
Nope. You will have to redo the restore and stop one step earlier.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bing" <bing@.discussions.microsoft.com> wrote in message
news:F9861F7C-1D50-40C7-8B83-3ECCDC838AD8@.microsoft.com...
> I just restored a db from its full backup and then applied its diff backup
> and a log backup. Now I need to know how the db looked like before the
log
> backup was applied. Is it possible to undo the restore from the log
backup?
> Thanks,
> Bing
and a log backup. Now I need to know how the db looked like before the log
backup was applied. Is it possible to undo the restore from the log backup?
Thanks,
Bing
Nope. You will have to redo the restore and stop one step earlier.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bing" <bing@.discussions.microsoft.com> wrote in message
news:F9861F7C-1D50-40C7-8B83-3ECCDC838AD8@.microsoft.com...
> I just restored a db from its full backup and then applied its diff backup
> and a log backup. Now I need to know how the db looked like before the
log
> backup was applied. Is it possible to undo the restore from the log
backup?
> Thanks,
> Bing
Subscribe to:
Posts (Atom)