SQL Server 2000 Developer Edition?

[hukarez]

Anyone happen to know what the deal is with this particular version? Someone's told me there's a certain perk about using this edition as opposed to standard or the like.

[Taco]

Is this the info that you are looking for?

http://www.microsoft.com/sql/howtobuy/development.asp

[hukarez]

Yeah, I checked it out and stuff. Though, I'm curious as to whether or not anyone's had any experience with SQL Server stuff. I'm confused by that whole licensing thing; more along the lines in the sense that you buy the software...and then a license, or is in included? I'm guessing it's included already and stuff - but just wanted to make sure, before I bother plunking down cash for it.

Figure, it'd be useful to have some kind of SQL environment...though I admit; I'm not much experienced when it comes to setting up SQL and all. Any help/advice would be appreciated; especially if you've got any experience with dealing with databases!

[Taco]

Licensing is definitely confusing. I have some experience with SQL Server. The way I understand it is - if you buy the Developer Edition, then you have a license to install it on one machine for development and testing purposes. You are not allowed to install it on any other computers, including customers for software that you have developed. In order to do that you'd have to purchase (or have the customer purchase) another license.

Installing SQL Server isn't too bad. It asks you a bunch of questions during the installation, but most of the defaults will work just fine for local development work. If you run into any problems let me know.

[Primal]

Correct you can only use the developer version for developing. If you need to use it on a production server you need to purchase CALs or Processer Licenses.

If you're just starting with SQL you may want to start out with MSDE (free download with SQL SP3). It Microsofts steping block to SQL. It's the exact same thing as a SQL database but its free. There are limits on it, such as you can only have 16 databases and after 5 concurrent connections there is a speed regulator on it (you really don't notice until you have a lot of users). But every thing else is EXACTLY the same as SQL.

So you can get started with MSDE (can even use enterprise manager to manage databases) and when you are really to move to the full SQL Server you can detach the database from MSDE and Attach it to the SQL server. No data loss, no rebuilding databases or stored procedures. The databases are SQL databases.

[hukarez]

MSDE? It's a free download with Microsoft SQL? I'll have to check that out. I figure, if I can somewhat simulate my work environment at home, I'll get a step up during the week.

[Primal]

http://www.microsoft.com/sql/msde/

[hukarez]

Thanks much, Primal for the input. I guess when I get that SQL Developer thing, I'll go right ahead and download that MSDE bit. You recommend any SQL related websites (aside from Microsoft ones) that would be good to check out?

[cartman]

And as a note, anyone installing SQL 2000, make sure you put SQL 2000 Service Pack 3 on, and avoid the SQL Slammer virus and its derivatives.

[hukarez]

Sage advice; luckily, if I read the packaging right, it mentioned something about SP3.0a or the like.

[hukarez]

So you can get started with MSDE (can even use enterprise manager to manage databases) and when you are really to move to the full SQL Server you can detach the database from MSDE and Attach it to the SQL server. No data loss, no rebuilding databases or stored procedures. The databases are SQL databases.
Probably a little too late to ask and all, but is SQL Server 2K a standalone installation, or something that supplements one's Windows OS?

[Tekneek]

Work with something else like mySQL instead. It's free and all the information you could need and use is readily available. Microsoft screws up SQL, at least as of the last time we fooled with it at work.

[Primal]

Probably a little too late to ask and all, but is SQL Server 2K a standalone installation, or something that supplements one's Windows OS?
You need an OS as well. I have my SQL servers on Windows 2003 servers. But you should be able to install it on 2000 or NT. If you're just installing the developer edition you can put it on XP as well.

[Primal]

Work with something else like mySQL instead. It's free and all the information you could need and use is readily available. Microsoft screws up SQL, at least as of the last time we fooled with it at work.
Lets not turn this in the a Microsoft vs. Anti-Microsoft pissing match.

[hukarez]

You need an OS as well. I have my SQL servers on Windows 2003 servers. But you should be able to install it on 2000 or NT. If you're just installing the developer edition you can put it on XP as well.
Okie doke, just wanted to make sure! Right now, the desktop's setup with a 2K OS, since from before, Visual Basic 6 wasn't working well with the initial XP setup. I suppose if I had another machine, I could get Server installed on it and put the SQL developer edition on that.

To elaborate:

I've got 2 machines, an XP laptop with .NET setup on it. The other machine is a desktop setup with 2K, with VB6 and .NET setup on it. I do more VB developing with the 2K machine, and figure I'd get SQL setup on the desktop - though I'm hoping such a setup wouldn't interfere with the environment and all. (Still new to the concept of SQL setups!)

[Primal]

You shouldn't have any trouble putting SQL on either of those machines. Developer edition doesn't need a server, a desktop OS will do.

Have fun.

[hukarez]

Excellent. Thanks again!