Going back to SQL Server 7...

Hi there! I have a PC with Windows XP Pro installed. I have it also with
SQL Server 2000. I'd like to install back SQL Server 7, but I keep getting
an error that Enterprise Manager.msc can't be installed.
Could someone shed some light on this? What are the steps I must take in
order to install SQL 7 (previous version).
Thanks for your time,
Felix
I believe that SQL Server 7.0 would have to be installed first, and then SQL
Server 2000 could be installed as a separate instance -- SQL Server 7.0 is
not instance-aware, so I doubt it can be installed second.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Flix Melndez" <fmelende@.ibw.com.ni> wrote in message
news:%23y8VwVGcFHA.1152@.tk2msftngp13.phx.gbl...
> Hi there! I have a PC with Windows XP Pro installed. I have it also with
> SQL Server 2000. I'd like to install back SQL Server 7, but I keep
getting
> an error that Enterprise Manager.msc can't be installed.
> Could someone shed some light on this? What are the steps I must take in
> order to install SQL 7 (previous version).
> Thanks for your time,
> Felix
>
>
|||Adam,
In other words, does this mean that I must reformat my PC?
Thanks for your time,
Felix
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> escribi en el
mensaje news:OMJxJcGcFHA.3204@.TK2MSFTNGP12.phx.gbl...
>I believe that SQL Server 7.0 would have to be installed first, and then
>SQL
> Server 2000 could be installed as a separate instance -- SQL Server 7.0 is
> not instance-aware, so I doubt it can be installed second.
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Flix Melndez" <fmelende@.ibw.com.ni> wrote in message
> news:%23y8VwVGcFHA.1152@.tk2msftngp13.phx.gbl...
> getting
>
|||No, absolutely not. What it means is that you might have to un-install SQL
Server 2000, then install SQL Server 7.0, then install SQL Server 7.0 SP4,
then re-install SQL Server 2000 and update to SP4. You can detach and back
up all of your databases first, then re-attach them when you're back up and
running.
Another option might be to use a Virtual PC for the SQL Server 7.0
installation. Have you considered that?
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Flix Melndez" <fmelende@.ibw.com.ni> wrote in message
news:%239r0roOcFHA.2980@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Adam,
> In other words, does this mean that I must reformat my PC?
> Thanks for your time,
> Felix
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> escribi en el
> mensaje news:OMJxJcGcFHA.3204@.TK2MSFTNGP12.phx.gbl...
is[vbcol=seagreen]
in
>
|||Flix,
You shouldn't need to format the machine. Delete everything from
c:\program files\Microsoft SQL Server. Delete everything in MSSQL7
directoy. Then go to the registry and remove everything relating to SQL
Server in there.
Reformatting your machine is an extreme measure, unless you have an
autobuild disk, and you can put it in while you go and have lunch... ;-)
See this article before you do anything:
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/?id=290991
The article applies to SQL2000, but the same principles apply to SQL7.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Flix Melndez wrote:
> Adam,
> In other words, does this mean that I must reformat my PC?
> Thanks for your time,
> Felix
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> escribi en el
> mensaje news:OMJxJcGcFHA.3204@.TK2MSFTNGP12.phx.gbl...
>
>
|||Mark,
Thanks a lot for your time and patience. I'll print and read the article
you state below.
On the other hand, before turning to the newsgroups, I indeed uninstalled
SQL Server 2000 and then tried installing back again SQL Server 7.0. But I
do not know why I began getting an error about "Enterprise Manager.msc" not
being configured correctly. As soon as I clicked on the OK, button, the
whole installation rolled back. Maybe I overlooked a step I had to take
(since I did not know about the article). I'll try to do it again... this
time following your advice.
Thanks again for your support.
Flix
"Mark Allison" <mark@.no.tinned.meat.mvps.org> escribi en el mensaje
news:e32R1yOcFHA.4048@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Flix,
> You shouldn't need to format the machine. Delete everything from
> c:\program files\Microsoft SQL Server. Delete everything in MSSQL7
> directoy. Then go to the registry and remove everything relating to SQL
> Server in there.
> Reformatting your machine is an extreme measure, unless you have an
> autobuild disk, and you can put it in while you go and have lunch... ;-)
> See this article before you do anything:
> How to manually remove SQL Server 2000 default, named, or virtual instance
> http://support.microsoft.com/?id=290991
> The article applies to SQL2000, but the same principles apply to SQL7.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Flix Melndez wrote:
|||Adam,
Thanks also a lot for your time and patience.
On the other hand, before turning to the newsgroups, I indeed uninstalled
SQL Server 2000 and then tried installing back again SQL Server 7.0. But I
do not know why I began getting an error about "Enterprise Manager.msc" not
being configured correctly. As soon as I clicked on the OK, button, the
whole installation rolled back.
Mark Allison also states that I should read the article about "Uninstalling
SQL Server 2000...".
I'll try to do it again... this time following both of your advices.
Thanks again for your support.
Flix
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> escribi en el
mensaje news:udgUnwOcFHA.3488@.tk2msftngp13.phx.gbl...
> No, absolutely not. What it means is that you might have to un-install
> SQL
> Server 2000, then install SQL Server 7.0, then install SQL Server 7.0 SP4,
> then re-install SQL Server 2000 and update to SP4. You can detach and
> back
> up all of your databases first, then re-attach them when you're back up
> and
> running.
> Another option might be to use a Virtual PC for the SQL Server 7.0
> installation. Have you considered that?
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Flix Melndez" <fmelende@.ibw.com.ni> wrote in message
> news:%239r0roOcFHA.2980@.TK2MSFTNGP10.phx.gbl...
> is
> in
>
|||Adam,
I don't want to seem I'm buggy, but... before trying to uninstall SQL Server
2000, please let me try to explain where this story all begins...
At work, we have some customers from outside the country. First I had in my
PC installed SQL Server 7.0 with Windows 2000 Professional. We currently
have a webserver with Windows 2000 Advanced Server with SQL Server 7.0. In
that server, we have some databases. As I was telling you, customers from
outside the country had access to this web server to run some web
applications. Since I develop such web applications from my PC, once I
develop something new or update some functionality, I have to copy the new
webpages or edited webpages back to the server as well as run some sql
scripts in order to update the database. I also have to reinstall the DLL
(data & business logic) in Component Services. After a while, I found out an
article about a configuration file that could be configured to point to a
test (my PC) or production (Server) database. I implemented this
configuration file with no hassle. Once in production, this configuration
file helped me to update just the webpages as well as the DLL, because this
time the user (transparently) connected via the webserver to my PC.
So far, so good!... then I reformatted my pc. This time I installed
Windows XP and SQL Server 2000 as well. Now when the customer wants to have
access to the database... the application just won't pass from the login
webpage. Then I suspected that this was due because of SQL Server 2000.
And even though I'm not very proficient with SQL Server I ended up believing
this is the main reason for not having access to the database as before. I
tested what I state before by accessing from another pc (my laptop which
also has Windows XP and SQL Server 2000). This time I have access to the
database.
In brief, the problem is... the Production Server has Windows 2000 Advanced
Server & SQL Server 7.0 installed on it and my PC has Windows XP and SQL
Server 2000 installed.
QUESTION:
Instead of just uninstalling SQL Server 2000 from my PC, is there a way to
access the databases that reside in my PC via the webserver (production
server) from another computer? Do I need to configure something at the
webserver or at my PC?
Thanks one more time for your time and patience
Flix
"Flix Melndez" <fmelende@.ibw.com.ni> escribi en el mensaje
news:uRJCsVPcFHA.3400@.tk2msftngp13.phx.gbl...
> Adam,
> Thanks also a lot for your time and patience.
> On the other hand, before turning to the newsgroups, I indeed uninstalled
> SQL Server 2000 and then tried installing back again SQL Server 7.0. But
> I do not know why I began getting an error about "Enterprise Manager.msc"
> not being configured correctly. As soon as I clicked on the OK, button,
> the whole installation rolled back.
> Mark Allison also states that I should read the article about
> "Uninstalling SQL Server 2000...".
> I'll try to do it again... this time following both of your advices.
> Thanks again for your support.
> Flix
>
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> escribi en el
> mensaje news:udgUnwOcFHA.3488@.tk2msftngp13.phx.gbl...
>