RE: Installing SP4 on SQL 2000

I think you are helping.
I have come across the acronym "RTM" but do not know what it means, what do
you mean "it should be at RTM version"?
--
Thanks
David G
Albury, Australia


"Mohit K. Gupta" wrote:

Hi David,

Sorry for late response, got really busy yesterday. I read the KB
article, it recommends saving the System databases, in case you have critical
information you need restored when you bring you server back to operations.

As you said this is a fresh install, so it should not be an issue.
Simiply uninstall, and if you feel that there were some extra clean needs to
be done as per the article feel free to do so.

If you are installing are installing a fresh version of SQL Server 2000,
it should be at RTM version. Simply upgrading it to SP4 should be good; if
you run into issues let me know.

FYI, the log files for SQL Server 2000 install are located in for my
various installs at ...

C:\Program FIles\Microsoft SQL Server\MSSQL\Install\*.out files.

Also at ..

C:\WINNT\SQL2000-KB948110-v8.00.2050-x86-ENU.log (SP4 Log Files)

Sorry I wasn't able to help with the original problem :(.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCITP: Database Administrator
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"David G" wrote:

I have only recently re-installed SQL on my machine, because I need it
instead of Access on a project I am doing. Fortunately, installing SP4 was
the first thing I have decided to do, so, as yet, there are no other
databases other than the default ones that ship with SQL Server. I haven't
even started building the first table.

Hopefully this will make things a little simpler. In anticipation I have
downloaded kb article 290991 "How to manually remove SQL Server 2000 default,
named or instance". As well as kb article 303747 "How to install SQL Server
2000 - Basic Local Installation".

I notice on page 1 of the removal kb that it lists a set of database files
that MUST be saved. I'm not sure why I would worry if I haven't used the
database for anything as yet. It also says I could use the setup program to
uninstall, perhaps I should try that, with the installation disk, first?

Any words of advice before I do this?
--
Thanks
David G
Albury, Australia


"Mohit K. Gupta" wrote:

I understand what you could be feeling. I think reinstalling would be the
best option. But before we reinstall following things to consider:

1) SQL Jobs running on the server (Backup jobs, and other tasks? GO to
Instance -> Mangement -> SQL Server Agent -> Jobs)
2) Number of user databases (System databases are master, model, msdb, and
tempdb; Example databases are pubs and Northwind)
3) The Security accounts. (How many accounts on the server? Go to Instance
-> Security -> Logins, how many logs exist there aside from SA,
BUILTIN\Administrator, will it be difficult for you to recreate these?)
4) Any DTS packages? (Go to Instance -> Data Transformation Services ->
Local Packages)

Since we will be wiping clean and starting over restoring the master
database might not be required depending on the answeres above.

Since this is your application, I am expecting this will be easy to get
restored and working.

Thanks.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCITP: Database Administrator
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"David G" wrote:

I have downloaded SP3a. I extracted all files to a folder I created called
SP3a. I double clicked Setup.bat, which consists of the code:
@echo off

start x86\setup\setupsql.exe

And, there was a brief flash of the DOS window, the mouse turned to an
hourglass for 3 or 4 seconds, and that was it. Nothing else, no dialogue
boxes, no nothing. I can honestly tell you this is becoming depressing.
I'm willing to continue because I need this database to be up and working on
my machine. Is the next suggestion to uninstall this installation and
reinstall it? Are there other suggestions?

--
Thanks
David G
Albury, Australia

.

Relevant Pages

  • RE: Installing SP4 on SQL 2000
    ... SQL Server 2000 SP3a, x86 ... It seems like there is issue on your install. ... MCITP: Database Administrator ... "David G" wrote: ...
    (microsoft.public.sqlserver.setup)
  • RE: Installing SP4 on SQL 2000
    ... maybe the install happens silently and everything has run ... "David G" wrote: ... Another place to check for install log files is in C:\Program ... should I have SQL Server on? ...
    (microsoft.public.sqlserver.setup)
  • Re: Why do I need to restart the SQL service?
    ... > I use Wise Installation utility to install MSDE 2000A. ... what I do within the app is: ... Check to see if the database exists. ... > SQL Server does not exist or access denied. ...
    (microsoft.public.sqlserver.msde)
  • Re: SQL SERVER 2008 Express + SP1
    ... Again there are three service pack setups which are provided by Microsoft. ... Are u sure you are using correct version for your install? ... DB Dev SQL Server 2005 ... Script level upgrade for database 'master' failed because upgrade step ...
    (microsoft.public.sqlserver.setup)
  • Re: sa password was inadvertently changed. With a kicker...
    ... Call the vendor of the new software product, and ask them what the> install script sets the SA password to when installing the product. ... Put the database files back where they should> be, ... >> I have a SQL Server 7 Standard edition server running in a ...
    (microsoft.public.sqlserver.security)