Model Database Status is 1073741824

After upgrade SQL Server 7 to SQL Server 2000, the model database status bec
omes 1073741824. What does it mean? I can create a new database in this stat
us. How do I change it?
Thanks
Walter> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean?
From the SQL Server 2000 Books Online
<herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.

> I can create a new database in this status. How do I change it?
I don't understand this part of your question. Please elaborate.
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean? I can create a new database in this
status. How do I change it?
> Thanks
> Walter|||After upgrade SQL Server from 7 to 2000, the server looks fine and I can cre
ate new database. However,the model database status is 1073741824 (cleanly s
hutdown) (before update SQL Server, the status is 0). It is a problem? Can I
say the upgrade is success
ful? Can I change the status and how to do?
"Dan Guzman" wrote:

> becomes 1073741824. What does it mean?
> From the SQL Server 2000 Books Online
> <herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.
>
> I don't understand this part of your question. Please elaborate.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Walter" <Walter@.discussions.microsoft.com> wrote in message
> news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> becomes 1073741824. What does it mean? I can create a new database in this
> status. How do I change it?
>
>|||Yes, this is a normal status for the model database. My test server, a new
SQL 2000 install, has status 1073741824.
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:AEE3D7B1-3FD3-4BC8-A656-25BC7F1E1382@.microsoft.com...
> After upgrade SQL Server from 7 to 2000, the server looks fine and I can
create new database. However,the model database status is 1073741824
(cleanly shutdown) (before update SQL Server, the status is 0). It is a
problem? Can I say the upgrade is successful? Can I change the status and
how to do?[vbcol=seagreen]
> "Dan Guzman" wrote:
>
status[vbcol=seagreen]
status[vbcol=seagreen]
this[vbcol=seagreen]sql

Model Database Status is 1073741824

After upgrade SQL Server 7 to SQL Server 2000, the model database status becomes 1073741824. What does it mean? I can create a new database in this status. How do I change it?
Thanks
Walter> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean?
From the SQL Server 2000 Books Online
<herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.
> I can create a new database in this status. How do I change it?
I don't understand this part of your question. Please elaborate.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean? I can create a new database in this
status. How do I change it?
> Thanks
> Walter|||After upgrade SQL Server from 7 to 2000, the server looks fine and I can create new database. However,the model database status is 1073741824 (cleanly shutdown) (before update SQL Server, the status is 0). It is a problem? Can I say the upgrade is successful? Can I change the status and how to do?
"Dan Guzman" wrote:
> > After upgrade SQL Server 7 to SQL Server 2000, the model database status
> becomes 1073741824. What does it mean?
> From the SQL Server 2000 Books Online
> <herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.
> > I can create a new database in this status. How do I change it?
> I don't understand this part of your question. Please elaborate.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Walter" <Walter@.discussions.microsoft.com> wrote in message
> news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> > After upgrade SQL Server 7 to SQL Server 2000, the model database status
> becomes 1073741824. What does it mean? I can create a new database in this
> status. How do I change it?
> >
> > Thanks
> > Walter
>
>|||Yes, this is a normal status for the model database. My test server, a new
SQL 2000 install, has status 1073741824.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:AEE3D7B1-3FD3-4BC8-A656-25BC7F1E1382@.microsoft.com...
> After upgrade SQL Server from 7 to 2000, the server looks fine and I can
create new database. However,the model database status is 1073741824
(cleanly shutdown) (before update SQL Server, the status is 0). It is a
problem? Can I say the upgrade is successful? Can I change the status and
how to do?
> "Dan Guzman" wrote:
> > > After upgrade SQL Server 7 to SQL Server 2000, the model database
status
> > becomes 1073741824. What does it mean?
> >
> > From the SQL Server 2000 Books Online
> > <herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.
> >
> > > I can create a new database in this status. How do I change it?
> >
> > I don't understand this part of your question. Please elaborate.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Walter" <Walter@.discussions.microsoft.com> wrote in message
> > news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> > > After upgrade SQL Server 7 to SQL Server 2000, the model database
status
> > becomes 1073741824. What does it mean? I can create a new database in
this
> > status. How do I change it?
> > >
> > > Thanks
> > > Walter
> >
> >
> >

Model Database Status is 1073741824

After upgrade SQL Server 7 to SQL Server 2000, the model database status becomes 1073741824. What does it mean? I can create a new database in this status. How do I change it?
Thanks
Walter
> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean?
From the SQL Server 2000 Books Online
<herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.

> I can create a new database in this status. How do I change it?
I don't understand this part of your question. Please elaborate.
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> After upgrade SQL Server 7 to SQL Server 2000, the model database status
becomes 1073741824. What does it mean? I can create a new database in this
status. How do I change it?
> Thanks
> Walter
|||After upgrade SQL Server from 7 to 2000, the server looks fine and I can create new database. However,the model database status is 1073741824 (cleanly shutdown) (before update SQL Server, the status is 0). It is a problem? Can I say the upgrade is success
ful? Can I change the status and how to do?
"Dan Guzman" wrote:

> becomes 1073741824. What does it mean?
> From the SQL Server 2000 Books Online
> <herf="tsqlref.chm::/ts_sys-d_5xrn.htm">, 1073741824 = cleanly shutdown.
>
> I don't understand this part of your question. Please elaborate.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Walter" <Walter@.discussions.microsoft.com> wrote in message
> news:E1EE009E-34CB-4681-935C-1B30B6DF1B52@.microsoft.com...
> becomes 1073741824. What does it mean? I can create a new database in this
> status. How do I change it?
>
>
|||Yes, this is a normal status for the model database. My test server, a new
SQL 2000 install, has status 1073741824.
Hope this helps.
Dan Guzman
SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:AEE3D7B1-3FD3-4BC8-A656-25BC7F1E1382@.microsoft.com...
> After upgrade SQL Server from 7 to 2000, the server looks fine and I can
create new database. However,the model database status is 1073741824
(cleanly shutdown) (before update SQL Server, the status is 0). It is a
problem? Can I say the upgrade is successful? Can I change the status and
how to do?[vbcol=seagreen]
> "Dan Guzman" wrote:
status[vbcol=seagreen]
status[vbcol=seagreen]
this[vbcol=seagreen]

Missing Program group

Guys and Girls
I have a server that was running SQL Server 2000 (on Windows 2000 server).
In preperation for an upgrade from an old SQL Server 6.5 system. I
un-installed 2000. I edited the registry to remove all references to SQL
Server and deleted all files.
I have run an install of 6.5. It seems to have worked all right except there
is no program groups on my start menu. Any ideas what might have happened?
Regards
Matt
"Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> Guys and Girls
> I have a server that was running SQL Server 2000 (on Windows 2000 server).
> In preperation for an upgrade from an old SQL Server 6.5 system. I
> un-installed 2000. I edited the registry to remove all references to SQL
> Server and deleted all files.
> I have run an install of 6.5. It seems to have worked all right except
there
> is no program groups on my start menu. Any ideas what might have happened?
> Regards
> Matt
Have you rebooted?
Rick Sawtell
MCT, MCSD, MCDBA
|||"Rick Sawtell" wrote:

> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> there
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:

> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> there
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Sounds like leftovers to me. Things like MDAC levels and such. You would
be better off reimaging the system. Also, you can't install 6.5 on Windows
2000, sorry. Scale it back down to NT 4.
Sincerely,
Anthony Thomas

"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:
[vbcol=seagreen]
> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
server).[vbcol=seagreen]
> there
happened?
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running sp5a.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:

> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on Windows
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
> server).
> happened?
>
>
|||Yes, but you're pushing technologies way beyond their design by doing that.
Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim that
7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
opposed to trying to compare Win NT 4 with either of the other OSes as well
as SS 6.5 with its counterparts.
Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
Anyway, in your case, apparently not. I would still recommend you reimage
the OS before attempting to reinstall 6.5. I've even had trouble with the
6.5 tools on workstations after 7.0 component had been installed. Even if
removed, I had trouble appling 6.5 service packs.
Then, again, you could always recreate them manually-I think it would be
quicker to reinstall the OS.
Sincerely,
Anthony Thomas

"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running
sp5a.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:

> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on
Windows[vbcol=seagreen]
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
> server).
QL
> happened?
>
>
|||Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and NT4.
Regards
Matt
"Anthony Thomas" wrote:

> Yes, but you're pushing technologies way beyond their design by doing that.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim that
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as well
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
> Windows
> QL
>
>
|||No, no, I got that. The problem is that you have already installed SS2K
components on that system. It would be a very valid test to start of with
configurations that your upgrade systems do not yet have on them.
However, I would recommend that you build new SS2K installations and then
use the Upgrade Wizard to migrate the data from one host to the next, NOT an
inplace upgrade. I have never had much luck with those and for the very
reason you are seeing now: too many old components and configurations
around. You would be better served starting fresh and just migrating the
contents. Then you can scrub the old box, rebuild it fresh for the next
migration.
Sincerely,
Anthony Thomas

"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:2B075981-64DA-4491-B616-9A5EE19C861E@.microsoft.com...
Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and
NT4.
Regards
Matt
"Anthony Thomas" wrote:

> Yes, but you're pushing technologies way beyond their design by doing
that.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim
that
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as
well[vbcol=seagreen]
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
would[vbcol=seagreen]
> Windows
S[vbcol=seagreen]
> QL
except
>
>

Missing Program group

Guys and Girls

I have a server that was running SQL Server 2000 (on Windows 2000
server).
In preperation for an upgrade from an old SQL Server 6.5 system. I
un-installed 2000. I edited the registry to remove all references to
SQL Server and deleted all files. I have rebooted the server.

I have run an install of 6.5. It seems to have worked all right except
there is no program groups on my start menu. Any ideas what might have
happened?

Regards

Matt<john.bandettini@.rbs.co.uk> wrote in message
news:1117786641.708591.159230@.g49g2000cwa.googlegr oups.com...
> Guys and Girls
> I have a server that was running SQL Server 2000 (on Windows 2000
> server).
> In preperation for an upgrade from an old SQL Server 6.5 system. I
> un-installed 2000. I edited the registry to remove all references to
> SQL Server and deleted all files. I have rebooted the server.
> I have run an install of 6.5. It seems to have worked all right except
> there is no program groups on my start menu. Any ideas what might have
> happened?
> Regards
> Matt

No idea, but presumably you can easily create your own group and add
shortcuts to the various executables? You could even copy the group from
another machine, if you have one available.

Simon

Missing Program group

Guys and Girls
I have a server that was running SQL Server 2000 (on Windows 2000 server).
In preperation for an upgrade from an old SQL Server 6.5 system. I
un-installed 2000. I edited the registry to remove all references to SQL
Server and deleted all files.
I have run an install of 6.5. It seems to have worked all right except there
is no program groups on my start menu. Any ideas what might have happened?
Regards
Matt"Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> Guys and Girls
> I have a server that was running SQL Server 2000 (on Windows 2000 server).
> In preperation for an upgrade from an old SQL Server 6.5 system. I
> un-installed 2000. I edited the registry to remove all references to SQL
> Server and deleted all files.
> I have run an install of 6.5. It seems to have worked all right except
there
> is no program groups on my start menu. Any ideas what might have happened?
> Regards
> Matt
Have you rebooted?
Rick Sawtell
MCT, MCSD, MCDBA|||"Rick Sawtell" wrote:
> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > Guys and Girls
> >
> > I have a server that was running SQL Server 2000 (on Windows 2000 server).
> > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > un-installed 2000. I edited the registry to remove all references to SQL
> > Server and deleted all files.
> >
> > I have run an install of 6.5. It seems to have worked all right except
> there
> > is no program groups on my start menu. Any ideas what might have happened?
> >
> > Regards
> >
> > Matt
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:
> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > Guys and Girls
> >
> > I have a server that was running SQL Server 2000 (on Windows 2000 server).
> > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > un-installed 2000. I edited the registry to remove all references to SQL
> > Server and deleted all files.
> >
> > I have run an install of 6.5. It seems to have worked all right except
> there
> > is no program groups on my start menu. Any ideas what might have happened?
> >
> > Regards
> >
> > Matt
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Sounds like leftovers to me. Things like MDAC levels and such. You would
be better off reimaging the system. Also, you can't install 6.5 on Windows
2000, sorry. Scale it back down to NT 4.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:
> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > Guys and Girls
> >
> > I have a server that was running SQL Server 2000 (on Windows 2000
server).
> > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > un-installed 2000. I edited the registry to remove all references to SQL
> > Server and deleted all files.
> >
> > I have run an install of 6.5. It seems to have worked all right except
> there
> > is no program groups on my start menu. Any ideas what might have
happened?
> >
> > Regards
> >
> > Matt
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running sp5a.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:
> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on Windows
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
> >
> > "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> > news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > > Guys and Girls
> > >
> > > I have a server that was running SQL Server 2000 (on Windows 2000
> server).
> > > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > > un-installed 2000. I edited the registry to remove all references to SQL
> > > Server and deleted all files.
> > >
> > > I have run an install of 6.5. It seems to have worked all right except
> > there
> > > is no program groups on my start menu. Any ideas what might have
> happened?
> > >
> > > Regards
> > >
> > > Matt
> >
> > Have you rebooted?
> >
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
> >
>
>|||Yes, but you're pushing technologies way beyond their design by doing that.
Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim that
7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
opposed to trying to compare Win NT 4 with either of the other OSes as well
as SS 6.5 with its counterparts.
Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
Anyway, in your case, apparently not. I would still recommend you reimage
the OS before attempting to reinstall 6.5. I've even had trouble with the
6.5 tools on workstations after 7.0 component had been installed. Even if
removed, I had trouble appling 6.5 service packs.
Then, again, you could always recreate them manually-I think it would be
quicker to reinstall the OS.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running
sp5a.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:
> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on
Windows
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
> >
> > "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> > news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > > Guys and Girls
> > >
> > > I have a server that was running SQL Server 2000 (on Windows 2000
> server).
> > > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > > un-installed 2000. I edited the registry to remove all references to S
QL
> > > Server and deleted all files.
> > >
> > > I have run an install of 6.5. It seems to have worked all right except
> > there
> > > is no program groups on my start menu. Any ideas what might have
> happened?
> > >
> > > Regards
> > >
> > > Matt
> >
> > Have you rebooted?
> >
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
> >
>
>|||Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and NT4.
Regards
Matt
"Anthony Thomas" wrote:
> Yes, but you're pushing technologies way beyond their design by doing that.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim that
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as well
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
> > Sounds like leftovers to me. Things like MDAC levels and such. You would
> > be better off reimaging the system. Also, you can't install 6.5 on
> Windows
> > 2000, sorry. Scale it back down to NT 4.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> > news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> > Rick
> >
> > Yes, several times.
> >
> > Regards
> >
> > Matt
> >
> > "Rick Sawtell" wrote:
> >
> > >
> > > "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> > > news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > > > Guys and Girls
> > > >
> > > > I have a server that was running SQL Server 2000 (on Windows 2000
> > server).
> > > > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > > > un-installed 2000. I edited the registry to remove all references to S
> QL
> > > > Server and deleted all files.
> > > >
> > > > I have run an install of 6.5. It seems to have worked all right except
> > > there
> > > > is no program groups on my start menu. Any ideas what might have
> > happened?
> > > >
> > > > Regards
> > > >
> > > > Matt
> > >
> > > Have you rebooted?
> > >
> > >
> > > Rick Sawtell
> > > MCT, MCSD, MCDBA
> > >
> > >
> > >
> > >
> >
> >
> >
>
>|||No, no, I got that. The problem is that you have already installed SS2K
components on that system. It would be a very valid test to start of with
configurations that your upgrade systems do not yet have on them.
However, I would recommend that you build new SS2K installations and then
use the Upgrade Wizard to migrate the data from one host to the next, NOT an
inplace upgrade. I have never had much luck with those and for the very
reason you are seeing now: too many old components and configurations
around. You would be better served starting fresh and just migrating the
contents. Then you can scrub the old box, rebuild it fresh for the next
migration.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:2B075981-64DA-4491-B616-9A5EE19C861E@.microsoft.com...
Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and
NT4.
Regards
Matt
"Anthony Thomas" wrote:
> Yes, but you're pushing technologies way beyond their design by doing
that.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim
that
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as
well
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
> > Sounds like leftovers to me. Things like MDAC levels and such. You
would
> > be better off reimaging the system. Also, you can't install 6.5 on
> Windows
> > 2000, sorry. Scale it back down to NT 4.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> > news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> > Rick
> >
> > Yes, several times.
> >
> > Regards
> >
> > Matt
> >
> > "Rick Sawtell" wrote:
> >
> > >
> > > "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> > > news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> > > > Guys and Girls
> > > >
> > > > I have a server that was running SQL Server 2000 (on Windows 2000
> > server).
> > > > In preperation for an upgrade from an old SQL Server 6.5 system. I
> > > > un-installed 2000. I edited the registry to remove all references to
S
> QL
> > > > Server and deleted all files.
> > > >
> > > > I have run an install of 6.5. It seems to have worked all right
except
> > > there
> > > > is no program groups on my start menu. Any ideas what might have
> > happened?
> > > >
> > > > Regards
> > > >
> > > > Matt
> > >
> > > Have you rebooted?
> > >
> > >
> > > Rick Sawtell
> > > MCT, MCSD, MCDBA
> > >
> > >
> > >
> > >
> >
> >
> >
>
>

Missing Program group

Guys and Girls
I have a server that was running SQL Server 2000 (on Windows 2000 server).
In preperation for an upgrade from an old SQL Server 6.5 system. I
un-installed 2000. I edited the registry to remove all references to SQL
Server and deleted all files.
I have run an install of 6.5. It seems to have worked all right except there
is no program groups on my start menu. Any ideas what might have happened?
Regards
Matt"Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> Guys and Girls
> I have a server that was running SQL Server 2000 (on Windows 2000 server).
> In preperation for an upgrade from an old SQL Server 6.5 system. I
> un-installed 2000. I edited the registry to remove all references to SQL
> Server and deleted all files.
> I have run an install of 6.5. It seems to have worked all right except
there
> is no program groups on my start menu. Any ideas what might have happened?
> Regards
> Matt
Have you rebooted?
Rick Sawtell
MCT, MCSD, MCDBA|||"Rick Sawtell" wrote:

> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> there
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:

> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
> there
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Sounds like leftovers to me. Things like MDAC levels and such. You would
be better off reimaging the system. Also, you can't install 6.5 on Windows
2000, sorry. Scale it back down to NT 4.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
Rick
Yes, several times.
Regards
Matt
"Rick Sawtell" wrote:

> "Matt Helm" <Matt Helm@.discussions.microsoft.com> wrote in message
> news:896F4725-DB82-4774-B600-30E75090F1A0@.microsoft.com...
server).[vbcol=seagreen]
> there
happened?[vbcol=seagreen]
> Have you rebooted?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running sp5a
.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:

> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on Window
s
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
>
> server).
> happened?
>
>|||Yes, but you're pushing technologies way beyond their design by doing that.
Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim that
7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
opposed to trying to compare Win NT 4 with either of the other OSes as well
as SS 6.5 with its counterparts.
Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
Anyway, in your case, apparently not. I would still recommend you reimage
the OS before attempting to reinstall 6.5. I've even had trouble with the
6.5 tools on workstations after 7.0 component had been installed. Even if
removed, I had trouble appling 6.5 service packs.
Then, again, you could always recreate them manually-I think it would be
quicker to reinstall the OS.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
Anthony
Thanks for the reply but 6.5 does run on W2K as long as you are running
sp5a.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
Regards
Matt
"Anthony Thomas" wrote:

> Sounds like leftovers to me. Things like MDAC levels and such. You would
> be better off reimaging the system. Also, you can't install 6.5 on
Windows
> 2000, sorry. Scale it back down to NT 4.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:DC23EBE0-2591-4EA8-A9C9-BDBA7972B0EC@.microsoft.com...
> Rick
> Yes, several times.
> Regards
> Matt
> "Rick Sawtell" wrote:
>
> server).
QL[vbcol=seagreen]
> happened?
>
>|||Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and NT
4.
Regards
Matt
"Anthony Thomas" wrote:

> Yes, but you're pushing technologies way beyond their design by doing that
.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim th
at
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as wel
l
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
>
> Windows
> QL
>
>|||No, no, I got that. The problem is that you have already installed SS2K
components on that system. It would be a very valid test to start of with
configurations that your upgrade systems do not yet have on them.
However, I would recommend that you build new SS2K installations and then
use the Upgrade Wizard to migrate the data from one host to the next, NOT an
inplace upgrade. I have never had much luck with those and for the very
reason you are seeing now: too many old components and configurations
around. You would be better served starting fresh and just migrating the
contents. Then you can scrub the old box, rebuild it fresh for the next
migration.
Sincerely,
Anthony Thomas
"Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
news:2B075981-64DA-4491-B616-9A5EE19C861E@.microsoft.com...
Anthony
You are probably right that I need to rebuild the operating system. I was
hoping not to. I perhaps should have explained that i was installing 6.5
before installing 2000. The server is going to be used to upgrade some old
legacy 6.5 databases to 2000 so that we can finally get away from 6.5 and
NT4.
Regards
Matt
"Anthony Thomas" wrote:

> Yes, but you're pushing technologies way beyond their design by doing
that.
> Hmm, 6.5 is supported on Win2K but 7.0 is not on Win2K3. I would claim
that
> 7.0 and SS2K are more similar to each other as well as Win2K and Win2K3 as
> opposed to trying to compare Win NT 4 with either of the other OSes as
well
> as SS 6.5 with its counterparts.
> Let's face it, 6.5 was an NT 4, even NT 3.51 technology.
> Anyway, in your case, apparently not. I would still recommend you reimage
> the OS before attempting to reinstall 6.5. I've even had trouble with the
> 6.5 tools on workstations after 7.0 component had been installed. Even if
> removed, I had trouble appling 6.5 service packs.
> Then, again, you could always recreate them manually-I think it would be
> quicker to reinstall the OS.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Matt helm" <Matthelm@.discussions.microsoft.com> wrote in message
> news:3AF2B053-0FF2-4161-8B30-3BD38C39B046@.microsoft.com...
> Anthony
> Thanks for the reply but 6.5 does run on W2K as long as you are running
> sp5a.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=8532
> Regards
> Matt
> "Anthony Thomas" wrote:
>
would[vbcol=seagreen]
> Windows
S[vbcol=seagreen]
> QL
except[vbcol=seagreen]
>
>

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:1/14/2008
Time:5:59:11 PM
User:N/A
Computer:ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 ?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue before
Here is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
************************************************** *****************************
*
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17311
Date: 1/14/2008
Time: 5:59:11 PM
User: N/A
Computer: ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 Â?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue beforeHere is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
*******************************************************************************
*
----
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Missing History for Jobs (msdb.dbo.sysjobhistory)

New server running our SQL... upgrade from Advanced 2000 to Enterprise
2003... our SQL Instance normally records all history (View History from Job
s
in SQL Agent). For some reason, currently unknown, history disappears every
so often. In this case, all history from 11/24 going backward is gone. All
history from 11/25 through today is here. This happened previously. Is
there any logical explanation for this? I'd settle for a server reboot, but
to my knowledge, this did not happen either.
Also there is a disk space problem on one of the drives. The msdb does not
touch that drive so, in my way of thinking the drive space issue cannot be
connected to the missing history (sysjobhistory). Is this logical to assume
?
An additional thought comes to mind. The jobs were imported from one server
to another. The owner was either the service account (with plenty of
permission) or the sa account, but the jobs were recreated from script using
the sa login. Could this have an effect on the job history?
--
Regards,
JamieAlso I believe this is happenning each week. Saturday night or Sunday
morning to be sure.
--
Regards,
Jamie
"thejamie" wrote:

> New server running our SQL... upgrade from Advanced 2000 to Enterprise
> 2003... our SQL Instance normally records all history (View History from J
obs
> in SQL Agent). For some reason, currently unknown, history disappears eve
ry
> so often. In this case, all history from 11/24 going backward is gone. A
ll
> history from 11/25 through today is here. This happened previously. Is
> there any logical explanation for this? I'd settle for a server reboot, b
ut
> to my knowledge, this did not happen either.
> Also there is a disk space problem on one of the drives. The msdb does no
t
> touch that drive so, in my way of thinking the drive space issue cannot be
> connected to the missing history (sysjobhistory). Is this logical to assu
me?
> An additional thought comes to mind. The jobs were imported from one serv
er
> to another. The owner was either the service account (with plenty of
> permission) or the sa account, but the jobs were recreated from script usi
ng
> the sa login. Could this have an effect on the job history?
> --
> Regards,
> Jamie|||thejamie,
Recreating the jobs would cause them to have a new job_id, so any history
records that might still exist in sysjobhistory will no longer join to
existing jobs. (If you still have your previous server and can figure out
the old job_id to new job_id mapping, you could update rowsn in your
sysjobhistory and all would be well.)
Also, make sure that your SQL Agent Properties - History settings are the
same on you new server as your old, or you will find SQL Agent (by default)
deleting history fairly frequently.
RLF
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:C078BDDA-ED20-4F42-AD0E-2FF1AED4EE7F@.microsoft.com...
> New server running our SQL... upgrade from Advanced 2000 to Enterprise
> 2003... our SQL Instance normally records all history (View History from
> Jobs
> in SQL Agent). For some reason, currently unknown, history disappears
> every
> so often. In this case, all history from 11/24 going backward is gone.
> All
> history from 11/25 through today is here. This happened previously. Is
> there any logical explanation for this? I'd settle for a server reboot,
> but
> to my knowledge, this did not happen either.
> Also there is a disk space problem on one of the drives. The msdb does
> not
> touch that drive so, in my way of thinking the drive space issue cannot be
> connected to the missing history (sysjobhistory). Is this logical to
> assume?
> An additional thought comes to mind. The jobs were imported from one
> server
> to another. The owner was either the service account (with plenty of
> permission) or the sa account, but the jobs were recreated from script
> using
> the sa login. Could this have an effect on the job history?
> --
> Regards,
> Jamie|||Thanks for the reply Russell. Actually, I moved the data over on 11/4. I
didn't expect any history to go back before the move. What bothers me is
that on Saturday I had history going back to 11/4. On Sunday, it extended
only from 11/25. Everything prior to 11/24 is wiped. It still exists in
sysjobhistory. I am not the sole DBA so it is possible that someone other
than myself wiped it, but I have to presume that is not the case. It isn't
vital. I can filter the log for a given job to get the history. The histor
y
was set to 1000 - I have lots of disk space at the moment so I moved it to
10000 and from 100 to 1000 on the rows. Still a mystery. I suspect that
the disk space on the one drive being low may have something to do with the
history disappearing.
--
Regards,
Jamie
"Russell Fields" wrote:

> thejamie,
> Recreating the jobs would cause them to have a new job_id, so any history
> records that might still exist in sysjobhistory will no longer join to
> existing jobs. (If you still have your previous server and can figure out
> the old job_id to new job_id mapping, you could update rowsn in your
> sysjobhistory and all would be well.)
> Also, make sure that your SQL Agent Properties - History settings are the
> same on you new server as your old, or you will find SQL Agent (by default
)
> deleting history fairly frequently.
> RLF
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:C078BDDA-ED20-4F42-AD0E-2FF1AED4EE7F@.microsoft.com...
>
>|||Jamie,
If the rows are still in sysjobhistory then they should connect to the jobs.
If the jobs will not show history further back than 11/24, then did someone
redeploy the jobs again, such that they got new job_ids?
RLF
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:A8C507C7-D1B6-46FF-AD2F-9E9EBCF829F5@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Russell. Actually, I moved the data over on 11/4. I
> didn't expect any history to go back before the move. What bothers me is
> that on Saturday I had history going back to 11/4. On Sunday, it extended
> only from 11/25. Everything prior to 11/24 is wiped. It still exists in
> sysjobhistory. I am not the sole DBA so it is possible that someone other
> than myself wiped it, but I have to presume that is not the case. It
> isn't
> vital. I can filter the log for a given job to get the history. The
> history
> was set to 1000 - I have lots of disk space at the moment so I moved it to
> 10000 and from 100 to 1000 on the rows. Still a mystery. I suspect that
> the disk space on the one drive being low may have something to do with
> the
> history disappearing.
> --
> Regards,
> Jamie
>
> "Russell Fields" wrote:
>|||Sounds very possible. Thanks.
--
Regards,
Jamie
"Russell Fields" wrote:

> Jamie,
> If the rows are still in sysjobhistory then they should connect to the job
s.
> If the jobs will not show history further back than 11/24, then did someon
e
> redeploy the jobs again, such that they got new job_ids?
> RLF
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:A8C507C7-D1B6-46FF-AD2F-9E9EBCF829F5@.microsoft.com...
>
>