MSDE 2000 Versions

I was wondering if any of you guys can kindly help me in finding all
the different versions of MSDE 2000 that came out since it's first
release. I expected to find something similar like Sun's archive
(http://java.sun.com/products/archive/index.html) for MSDE 2000 too
but failed to find after a few hours of browsing at the Microsoft
Download Center (http://www.microsoft.com/downloads/...displaylang=en).
They seem more into promoting their new MSDE 2000 Release A for the
time being but nothing much about the previous versions of MSDE to
serve my product testing purposes.
All I need is a complete list of different versions of MSDE 2000 with
downloadable links.

Thanks in advance.

IzzYHi Izzy,

MSDE Release A is the first version of MSDE that is actually available for
free download. All previous versions of MSDE came as part of the license for
another Microsoft product, like SQL Server, Office Professional and Web
Matrix.

Also it is Microsoft's policy to have nothing but the most recent version of
a Service Pack available for download, because Service Packs include
important fixes, like for example the fix for the Slammer worm.

As MSDE is intended for use in self contained applications, you should have
an MSDE instance just for use with your own application (you can have 16
instances of MSDE on one machine). Because your application is the only one
that uses that MSDE instance, you can upgrade it at will and the best way of
doing things is to include the latest Service Pack in your installation and
upgrade package. In this way you only have to test your software against the
latest version of MSDE and you don't put your customers at risk of being
infected by Slammer.

--
Jacco Schalkwijk
SQL Server MVP

"izzy" <izzy@.eudoramail.com> wrote in message
news:330ce184.0312172245.6f84b998@.posting.google.c om...
> I was wondering if any of you guys can kindly help me in finding all
> the different versions of MSDE 2000 that came out since it's first
> release. I expected to find something similar like Sun's archive
> (http://java.sun.com/products/archive/index.html) for MSDE 2000 too
> but failed to find after a few hours of browsing at the Microsoft
> Download Center
(http://www.microsoft.com/downloads/...displaylang=en).
> They seem more into promoting their new MSDE 2000 Release A for the
> time being but nothing much about the previous versions of MSDE to
> serve my product testing purposes.
> All I need is a complete list of different versions of MSDE 2000 with
> downloadable links.
> Thanks in advance.
> IzzYsql

MSDE 2000 Versions

I was wondering if any of you guys can kindly help me in finding all
the different versions of MSDE 2000 that came out since it's first
release. I expected to find something similar like Sun's archive
(http://java.sun.com/products/archive/index.html) for MSDE 2000 too
but failed to find after a few hours of browsing at the Microsoft
Download Center (http://www.microsoft.com/downloads/search.aspx?displaylang=en).
They seem more into promoting their new MSDE 2000 Release A for the
time being but nothing much about the previous versions of MSDE to
serve my product testing purposes.
All I need is a complete list of different versions of MSDE 2000 with
downloadable links.
Thanks in advance.
IzzYHi Izzy,
MSDE Release A is the first version of MSDE that is actually available for
free download. All previous versions of MSDE came as part of the license for
another Microsoft product, like SQL Server, Office Professional and Web
Matrix.
Also it is Microsoft's policy to have nothing but the most recent version of
a Service Pack available for download, because Service Packs include
important fixes, like for example the fix for the Slammer worm.
As MSDE is intended for use in self contained applications, you should have
an MSDE instance just for use with your own application (you can have 16
instances of MSDE on one machine). Because your application is the only one
that uses that MSDE instance, you can upgrade it at will and the best way of
doing things is to include the latest Service Pack in your installation and
upgrade package. In this way you only have to test your software against the
latest version of MSDE and you don't put your customers at risk of being
infected by Slammer.
Jacco Schalkwijk
SQL Server MVP
"izzy" <izzy@.eudoramail.com> wrote in message
news:330ce184.0312172245.6f84b998@.posting.google.com...
> I was wondering if any of you guys can kindly help me in finding all
> the different versions of MSDE 2000 that came out since it's first
> release. I expected to find something similar like Sun's archive
> (http://java.sun.com/products/archive/index.html) for MSDE 2000 too
> but failed to find after a few hours of browsing at the Microsoft
> Download Center
(http://www.microsoft.com/downloads/search.aspx?displaylang=en).
> They seem more into promoting their new MSDE 2000 Release A for the
> time being but nothing much about the previous versions of MSDE to
> serve my product testing purposes.
> All I need is a complete list of different versions of MSDE 2000 with
> downloadable links.
> Thanks in advance.
> IzzY

MSDE 2000 Release A and Windows Installer

I am currently writing an installer for our product, which needs to incorporate MSDE 2000.
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc

MSDE 2000 Release A - Query Analyzer included?

I installed MSDE 2000 Release A, but can't find the Query Analyzer. Is it
included, or only available with other SQL Server versions. If it is
included, then how do I install it? If not, can I download it from somewhere
else?
Hi
MSDE 2000 does not come with any of the tools like Query Analyzer or
Enterprise Manager.
You could download the evaluation edition of SQL Server 2000 and use those
tools for 120 days.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Steve" <Steve@.discussions.microsoft.com> wrote in message
news:41977C7A-205A-4CDA-AD56-843DF8779DE6@.microsoft.com...
>I installed MSDE 2000 Release A, but can't find the Query Analyzer. Is it
> included, or only available with other SQL Server versions. If it is
> included, then how do I install it? If not, can I download it from
> somewhere
> else?
>

MSDE 1 or MSDE 2K ?

I want to experiment a little bit with the MSDE. I'll be working with
it strictly from Visual Basic 6.
I have both versions of MSDE available for installation (on
Windows2K). Which one should I use?
hi Martin,
"Martin" <martinvalley@.comcast.net> ha scritto nel messaggio
news:ku03605ao6d7v7o4vt9op58f1ob6f88m52@.4ax.com...
> I want to experiment a little bit with the MSDE. I'll be working with
> it strictly from Visual Basic 6.
> I have both versions of MSDE available for installation (on
> Windows2K). Which one should I use?
as MSDE 1.0 is base on SQL Server 2000 and is currently only in maintenance,
I'd stick with the live one, MSDE 2000, which is full supported and is
plenty of new features with regards to the SQL Server 7.0 code base...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||are things mixed up?
|||minor correction in <>
as MSDE 1.0 is base on SQL <Server 7.0> and is currently only in
maintenance,
I'd stick with the live one, MSDE 2000 (<based on SQL Server 2000>), which
is full supported and is
plenty of new features with regards to the SQL Server 7.0 code base...
MSDE 2000 (latest release) is available from
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Dave.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:84CAA9BC-DE4F-4779-BE75-B6B715F4A6B4@.microsoft.com...
> are things mixed up?

MSDE 1 => msde 2 => MSDE 2 SP3a

I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
the command-line parameters to upgrade MSDE 2 to a newer version of MSDE 2,
at least not retaining my Office Server Extensions database. Considering
that SP 4 for MSDE 2 will probably be out soon, what's the proper method to
upgrade MSDE 2 when it was used to upgrade MSDE 1?
Well, I figured out the easy way to do things. First, you install MSDE 2.
Then you install office server extensions using the /nd switch to avoid
installing an older version of MSDE. Had a lot of registry cleaning to do,
had to unregister ows.dll, and a few other problems to fix before I could
get a successful install of OSE. Works fine, though. I was even able to
apply the OSE SP3 patch.
"Ellen Langton" <elangton@.wctc.net> wrote in message
news:emnXe$XCFHA.3688@.TK2MSFTNGP14.phx.gbl...
> I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
> MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
> the command-line parameters to upgrade MSDE 2 to a newer version of MSDE
2,
> at least not retaining my Office Server Extensions database. Considering
> that SP 4 for MSDE 2 will probably be out soon, what's the proper method
to
> upgrade MSDE 2 when it was used to upgrade MSDE 1?
>
|||Well, I figured out the easy way to do things. First, you install MSDE 2.
Then you install office server extensions using the /nd switch to avoid
installing an older version of MSDE. Had a lot of registry cleaning to do,
had to unregister ows.dll, and a few other problems to fix before I could
get a successful install of OSE. Works fine, though. I was even able to
apply the OSE SP3 patch.
"Ellen Langton" <elangton@.wctc.net> wrote in message
news:emnXe$XCFHA.3688@.TK2MSFTNGP14.phx.gbl...
> I'm able to successfully upgrade my MSDE 1 installation from Office 2k to
> MSDE 2, using any of the versions 1 thru 3a. However, I can't figure out
> the command-line parameters to upgrade MSDE 2 to a newer version of MSDE
2,
> at least not retaining my Office Server Extensions database. Considering
> that SP 4 for MSDE 2 will probably be out soon, what's the proper method
to
> upgrade MSDE 2 when it was used to upgrade MSDE 1?
>

MSDE - Multiple versions coexist?

While setting up for HP Insight Manager...
Microsoft provided documentation is leading me to believe that MSDE 2000 SP3
and previous versions of MSDE could coexist on one box.
Is that true?
I installed MSDE 2000 SP3 on one of my servers which had a previous MSDE
version with existing active databases. The result was that though databases
were still running, I had difficulty seeing the certain databases through
Enterprise Manager.
hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:O7wPFHaoEHA.2032@.TK2MSFTNGP10.phx.gbl
> While setting up for HP Insight Manager...
> Microsoft provided documentation is leading me to believe that MSDE
> 2000 SP3 and previous versions of MSDE could coexist on one box.
> Is that true?
> I installed MSDE 2000 SP3 on one of my servers which had a previous
> MSDE version with existing active databases. The result was that
> though databases were still running, I had difficulty seeing the
> certain databases through Enterprise Manager.
yese , up to 16 instances of SQL Server 2000 and MSDE 2000 at different
service pack level can coexist on the same box.
1 instance will be the default instance, locally available as "(local)" or
generally available as "ComputerName", while all other instances will be
named instances, reachable with teir complete name, made up by the computer
name and instance name, in the form "ComputerName\InstanceName"
what kind of problem are you facing?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have a server running MSDE and two existing databases or instances. I am
uncertain of the version or how to determine the version.
I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
installed MSDE 2000, SP3 and created the new instance for Insight Manager.
The application worked and the existing databases/instances were accessible
and continued to work.
A few days later, an Programmer/Administrator was trying to
monitor/manipulate one of the previously existing databases via Enterprise
Manager and noticed he could not see it the applications utilizing the
databases worked fine.
I uninstalled the MSDE 2003. The Programmer/Administrator then was able to
monitor/manipulate the previously existing databases via Enterprise Manager.
I'm not certain my explanation is clear. Any help you can provide is
appreciated.
DWM
[vbcol=seagreen]
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rgrn3F1ad8ggU1@.uni-berlin.de...
> hi,
> what kind of problem are you facing?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
|||hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:%23$d0IXkoEHA.3464@.tk2msftngp13.phx.gbl
> I have a server running MSDE and two existing databases or instances.
> I am uncertain of the version or how to determine the version.
> I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
> installed MSDE 2000, SP3 and created the new instance for Insight
> Manager. The application worked and the existing databases/instances
> were accessible and continued to work.
> A few days later, an Programmer/Administrator was trying to
> monitor/manipulate one of the previously existing databases via
> Enterprise Manager and noticed he could not see it the applications
> utilizing the databases worked fine.
> I uninstalled the MSDE 2003. The Programmer/Administrator then was
> able to monitor/manipulate the previously existing databases via
> Enterprise Manager.
> I'm not certain my explanation is clear. Any help you can provide is
> appreciated.
actually there's no reason for that... all instances can be running
(resources allowing it) with no consequences...
each instace will have it's onw TCP address , provided by the service
listening on UDP 1434 port..
check the services (SQL Server services) are running and address each
instance with it's correct name (full name for named instance)
I do not know HP Insight manager, so I'm not able to provide fupport for
that tool/application
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

msdb..backupset.backup_finish_date -- changes from SQL2000?

It appears that the behavior has changed for the backupset table in the MSDB database between versions.

In SQL2000 backup_start_date & backup_finish_date were populated correctly. In 2005, backup_finish_date is the same as the backup_start_date value. Is this a bug or should I be looking for my backup timing elsewhere in 2005?

Thank you.

I can't repro the problem. It works fine for me.

I use this query to get a quick look at timings.

select top 100 database_name, backup_set_id, type, backup_finish_date, backup_start_date,
datediff (second,backup_start_date, backup_finish_date) secondsToComplete
,convert (bigint, backup_size / 1048576 ) sizeInMB

from msdb..backupset
where type = 'D'
order by backup_finish_date desc

If you can describe a repro, please let us know.

|||

It appears to work fine for database backups, I see timing differences in them. However for log backups (type = 'L') it appears that it's not changing, but I'm still investigating.

I was originally pursuing a long running t-log backup time and that's how I noticed this behavior. I've since discovered that if a backup device has a large # of backups appended to it, it dramaticly effects the time it takes to perform the backup. I was suprised to find that the finish time was being reported as the same as the start time when it clearly was taking much longer to perform the backup...

Currently (and with a small # of appends), my backups are averaging around 1/10th second so I'll have to try to dummy up some logspace and see if it's just that my backups are running quicker than the process can account for, or if it is indeed a bug.

I'll have more in a day or so once I can get some testing done. Thank you for looking into this.

|||

Your info helps.

Our start/finish times do NOT include the time it takes to open the media set and prepare it for writing.

The time only includes the time that is actually spent transferring data. This is the same logic as exists in sql2000.

For example, it may take many minutes to open a tape drive and seek to the end when appending data. That time is not included.

So if you want to also include that time, you'll need to add your own start/stop time.

This might already work if you use sqlagent jobs, and look up the start/top time in the job history.

Are you backing up to tape? That will always be relatively slow, and gets worse when appending backups.

If you have a lot of backups to append in a batch, such as a nightly job, you can use BACKUP WITH NOREWIND which avoids all the time to REWIND/SEEK to end that happens in such a scenario.

If you are backing up to disk, then having a lot of backups in the file shouldn't really matter...to a point.

1000's of backups WILL result in significant delay. The reason is that when setting up for the backup, we perform a synchronous read of all the marks before/after each backup set.

For disk backups, my recommendation is to prefer the use of a single filesystem directory, then write each backup into a separate disk file. That gives you better control over retention and space management. But I'd agree that it might be slightly more work to wrap this in your backup jobs. If you are using our management tools, they already do this by naming the log backups as ***.TRN where the *** includes the database name and timestamp of the backup.

Hope that helps.