Microsoft SQL Server 2000 SP4 is open for Public Beta

Microsoft SQL Server 2000 SP4 is open for Public Beta Testing
Sign up to test drive the newest service pack for SQL Server 2000 give us
your feedback. SQL Server 2000 SP4 is now open for public beta testing.
Instructions on how to signup for this beta program are below.
SQL Server 2000 Service Pack 4
SQL Server 2000 Service Pack 4 (SP4) includes a roll-up of bug fixes, added
platform support for AMD64, and Intel Extended Platforms in WOW so you can
use 32-bit applications on 64-bit architectures. This is the first service
pack to service the 64-bit release of SQL Server. SP4 is suitable for all
SQL Server 2000 customers who want to update their existing installations to
incorporate all changes since SP3a.
Who should participate?
Customers who want to use their 32-bit applications on 64-bit
hardware should consider the SQL Server 2000 SP4 beta.
Customers who want to update to this latest SQL Server 2000
service pack level, SP4 should consider the SP4 beta.
Instructions for Signing up for the Beta
To sign up for Microsoft's beta program for SQL Server 2000 SP4, go to the
following link, http://www.microsoft.com/sql/evaluat...ominations.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
And we'll be hosting a public chat on the contents of Service Pack 4 on
February 15th at 2pm Pacific Time. It's listed at
http://www.microsoft.com/technet/com...s/default.mspx
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tara Nerurkar" <a-tarane@.online.microsoft.com> wrote in message
news:%23j1%23yWyAFHA.3836@.tk2msftngp13.phx.gbl...
> Microsoft SQL Server 2000 SP4 is open for Public Beta Testing
>
> Sign up to test drive the newest service pack for SQL Server 2000 give us
> your feedback. SQL Server 2000 SP4 is now open for public beta testing.
> Instructions on how to signup for this beta program are below.
>
> SQL Server 2000 Service Pack 4
>
> SQL Server 2000 Service Pack 4 (SP4) includes a roll-up of bug fixes,
> added platform support for AMD64, and Intel Extended Platforms in WOW so
> you can use 32-bit applications on 64-bit architectures. This is the first
> service pack to service the 64-bit release of SQL Server. SP4 is suitable
> for all SQL Server 2000 customers who want to update their existing
> installations to incorporate all changes since SP3a.
>
> Who should participate?
> Customers who want to use their 32-bit applications on 64-bit
> hardware should consider the SQL Server 2000 SP4 beta.
> Customers who want to update to this latest SQL Server 2000
> service pack level, SP4 should consider the SP4 beta.
>
>
> Instructions for Signing up for the Beta
> To sign up for Microsoft's beta program for SQL Server 2000 SP4, go to the
> following link,
> http://www.microsoft.com/sql/evaluat...ominations.asp
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
sql

Microsoft SQL Server 2000 Desktop Engine

Trying to install Microsoft SQL Server 2000 Desktop Engine on my laptop. I downloaded the software and opened it to a folder on the C drive. Then from the command prompt I entered this:

C:\msderela>setup sapwd = hillary instancename=mjh targetdir=c:\mike

The program starts to install and seems to get near to the end of instal and then the progress bar starts going backwards and nothing gets installed...any ideas of what I'm doing wrong...I really don't know anything about this at all.

ThanksSounds like you've tried it a couple of time already, huh?

Bounce the box, see what you got :)|||Like I said...I know nothing about this...bounce the box? sorry for being so stupid|||ummm. Reboot? Restart? Unplug and then re-plug? Either one will work ;)|||Originally posted by rdjabarov
Sounds like you've tried it a couple of time already, huh?

Bounce the box, see what you got :)

Is it possible to do if it does not look like a box (laptop)... ;)|||I've rebooted several times and still get the same results...|||What is the OS on your laptop?|||2000 pro|||progress bar going backwards?? check if the monitor is kept upside down??|||Thanks....|||I don't know if this will help but I have attached the error log. I don't understand what it is saying.|||Where is your log file?|||I'm sending the file again|||Do you have enough hard disk space?|||I have 2.43 GB|||I'm wondering if the problem is
C:\msderela>setup sapwd = hillary instancename=mjh targetdir=c:\mike

I pasted the text from Microsoft website:

TARGETDIR="executable_folder_path"

Specifies the folder where the Desktop Engine executable files are to be installed. The default for executable_folder_path when installing a default instance is C:\Program Files\Microsoft SQL Server\MSSQL\Binn\. The default for executable_folder_path when installing a named instance is C:\Program Files\Microsoft SQL Server\MSSQL$<InstanceName>\Binn\, where <InstanceName> is the name specified in the INSTANCENAME option. The file path for this parameter must end with a backslash (\).

Read the details at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp|||Nope...still won't install|||Did you try to click the file Setup.exe for the installation and use the default folder?

Microsoft iSCSI Initiator & SQL Server services

Hello all,
I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN.
It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.

Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with.
Could any one has any real solution or had encounter such a problem before?

Any help is appreciated.

Thanks bunch!
imransi.Looks like your SQL Service starts before your SAN is available.|||Originally posted by rdjabarov
Looks like your SQL Service starts before your SAN is available.

You are 100% right. So thats why we are restarting SQL services.
We can manually start sql services but thats not what we wnat and really thsi should not be the solutuion ;)|||See if you can "impose" a dependency on MSSQLSERVER service in regards to this SAN service.