Does anyone know if the 2008 Developer edition of SQL Server allows you to have multiple developers access it on the same server? I called Microsoft, but the guy I talked to didn't seem to know the answer. Has anyone tried it?
I am a developer that uses the Express edition now on one server and all four of our developers use it in our LAN. If the Developer edition allows me to do the same thing, but with all the extra features of Enterprise, then for $50 I'll buy it.
Sure - the Developer edition is really just the Enterprise edition without the licensing rights to use it in production or roll it out in a system. But it's a full-fledged SQL Server, which supports concurrent users and tons of databases on a single server.
Every dev can have their own database (e.g. APP_JOE, APP_PETE, APP_SCOTT etc.) or they can access a common development database - whatever strikes your fancy.
Each person using it needs to have a license, I believe, but there is no technical limitation on allowing other users access to it.
AFAIK, the Developer Edition of SQL Server is functionally equivalent to Enterprise, but only licensed for Development work, not production. It should behave like the Enterprise edition, including allowing access by multiple users/applications.
You'd have to read the license agreement to be sure, but if memory serves, it says you can have up to 10 concurrent users.
Related
At my workplace we just upgraded to SQL Server 2008 R2 Advanced in our development server using the product key of the MSDN subscription, and we want to install the full developer tools (Management Studio & Profiler) in several workstations as we had with the 2005 edition.
The problem is that the setup of the 2008 edition ask for a product key before selecting the components that you want to install, and we want to know if is allowed using the same key that we used for the server just for installing the developer tools.
If not, there is a way on installing (legally) the SQL Server Profiler in several workstations without having a different key for each one? (we only have a couple of keys from the the MSDN subscription).
I don't think so. I think it's pretty clear that MSFT expects each developer to have their own MSDN Subscription:
http://msdn.microsoft.com/subscriptions/cc150618.aspx
MSDN subscriptions are licensed on a per-user basis. One person can use the software to design, develop, test, or demonstrate his or her programs on any number of devices. Each person who uses the software this way needs a license.
I think it's OK to have developers running just express editions, but they shouldn't be taking advantage of any MSDN benefits they don't have a subscription for. As Chris stated, you should probably ask your sales rep if you think sharing tools like the profiler might be OK.
I've got experience with MySQL, DB2, and Oracle, but aside from writing a few queries, I've never used SQL Server.
My question is a three parter:
1) For a developer, what are some good "free" client tools to look at, and why (by "free" I mean open source, freeware, or the tools that come with SQL Server itself)?
2) I plan to run Developer or Express Edition on my workstation for development, and either Standard or Enterprise Edition in the testing and production environments. What methods exist if any for transferring data between different servers and the different editions?
3) Are there any common pitfalls that someone like me (who is used to the other database systems that I mentioned) might encountered during development?
TIA
SQL Server Express with tools.
All editions have the same SQL language features and code is 100% portable between them. There are 3rd party tools to synch changes, but moving entire DBs is easy using inbuilt tools.
Nah. The problem with databases is SQL and set theory, not the choice of RDBMS. If you understand databases/SQL you'll be OK.
SQL Server Management Studio which comes with SQL Server (any editions), or you can download it separately. SQL Server Profiler which doesn't come with Express.
Management studio has tools for backup/restore database. You can also consider detach/attach method to synchronize db .
It's hard to say. But if you had Mysql experience you will be pleasantly surprised by SQL Server.
UPDATE
There are so many things that each DB vendor implements differently that it's really hard to focus on some of them. One thing I was not used before is that SQL Server doesn't let unique columns to have more than 1 NULL value(there is a workaround though)
DO these versions mean anything to me as a developer? I understand they have limitations on connections/processors/etc but none of that matters to me for a local development instance. All of the ISOs on MSDN are the same size, does it make a difference which of these I choose to download?
The Developer edition is identical to the Enterprise edition, so you get all the feature you'll probably ever need. It's just not licensed for production use.
Standard edition (and Web edition) are somewhat limited in their functionality.
Developer Edition for 2014 and 2016 is available at no cost, so I'd definitely pick that one, if you need a dev platform!
The difference is in licensing mostly (Developer vs. Enterprise).
For development you wish to have the engine with all bells and whistles enabled, that is either Enterprise or Developer.
If you're only developing for customers then Developer will suffice. You hand-over the project to the customer and don't put it to operation yourself.
If it's your own product, then you will need un-Developer version sooner or later. By the moment of putting the software in production latest, that is.
Developer is fine for development but can't be used in production systems for lisencing reasons. It's a lot cheaper than the others too.
Use the development version as it will allow you to develop with features that are available on all of the production versions. If you were to install say just the Standard version then you would be unable to develop anything that uses an Enterprise feature.
http://www.microsoft.com/Sqlserver/2005/en/us/compare-features.aspx
As of today Developer Edition is free of cost.Further you can sign into Visual studio dev essentials and get for free VS community Edition,Microsoft R server Developer edition,Free xamarin,free 25$ monthly Azure credit and much more for free...
https://blogs.technet.microsoft.com/dataplatforminsider/2016/03/31/microsoft-sql-server-developer-edition-is-now-free/
As far as I know, the developer edition of SQL Server is available to everyone. I cannot seem to locate the download anywhere though! I have a technet plus, but even there I don't see the developer edition. I need the developer edition for the enterprise-only features, or I'd use SQL Server Express.
Update 1. I am NOTlooking for SQL express.
Update 2. I have tried Google (extensively)
There is no special licencing (like Academic) to buy Developer edition. The only difference is that the EULA licence included states you cannot use the software for production environments (only for testing/development).
Want to buy it?
Microsoft Store ($49.95, same price as Amazon used to sell 2005 Developer for)
Edit: Just to clarify, Developer Edition is not a free product. Some of the MSDN subscriptions (which cost far more then $49.95) include it as a perk, but it is still a shrink wrapped retail product as far as Microsoft is concerned.
Try this: https://www.microsoft.com/sqlserver/2008/en/us/developer.aspx
Ryan
While this isn't really programming related, I'll answer anyway.
The developer edition is not, in fact, available to everyone. To the best of my knowledge, the only way to obtain it is via an MSDN subscription (not TechNet, I don't think; sorry!) that includes server software (so something above the "Operating Systems" subscription level).
I'll give you the benefit of the doubt and assume that your need for the enterprise only features is for a development environment and that the deployment environment has a valid license for the enterprise edition. If that's the case, then you'll have to obtain an MSDN subscription.
Out of curiousity, what "enterprise only" features are you planning on using? In my experience, a fairly small percentage of developers actually need anything above the functionality offered in the Standard edition.
You definitely get developer edition via microsoft's MSDNAA academic program.
Developer edition is essentially the enterprise edition with license restrictions.
Use enterprise edition then.
If you have no license for enterprise edition, you will anyway not be able to use in production whatever you come up with in developer edition.
If you don't care about licenses, you can probably download it from anywhere you find. But then google is a better place to ask than SO community.
EDIT: You cannot legally get either developer of enterprise edition for free. If your customer does not give you a license, and if you don't buy one yourself, you have no legal options to perform this job.
Just wondering if it's worth it for a developer to use SQL Server 2005/2008 Developer Edition instead of the bundled SQL Server Express edition that comes with Visual Studio. I'm talking about for initial development of a website, where you need to create SQL scripts to generate the tables and things like that. I know with Express it's easy to add an .mdf file to your project and program against that, but wouldn't it be better to install Developer edition and program against a "real" database that would mimic what you're going to be using in production? That way if you're using VS Professional and can create a "database project" you can include all of your creation scripts and run them in production to recreate the environment.
If you have access to it, you're better off using Developer Edition because it supports more features and larger databases. For example, if you want to restore a 50gb database from your production server onto your workstation to do testing, you'll need Developer Edition.
Another example is if you're working with Enterprise-only features like partitioning, compression or the Resource Governor. Those features aren't available in Express, but they are available in Developer Edition.
If it is good enough for production then how can it be insufficient in development. And SQL Express is quite capable of handling fair loads (the kind of loads that would have stressed serious hardware just a few years ago).
SQL Server Express does not require licensing but has a smaller set of features.
Developing against full SQL Server (and Developer Edition matches Enterprise Edition) always leaves the chance that you rely on some feature that is not in the production edition.
At the very least all your testing (including unit testing) should happen against the edition to be used in production.
In this question, since a "full" version is being targeted for production then developer edition should be a good match, just be careful of enterprise features if you will deploy against Standard.
Personally, I think your development environment should look like as much as you can to your production environment.
SQL Server Express edition
has many limitations like size of database, supports only one processor, etc. It is the "lite" version of SQL Server
SQL Server Developer edition
is basically Enterprise edition but it cannot be used for production.
Be aware that if the success of your backend database relies on the use of enterprise features for development, and you want the same features on production, this will require enterprise license.
It depends on what you are doing. In general, I would say it is fine. If you can get a copy of Developer, I would recommend that route, but a great majority of your work can be done in Express.
Express has basic Reporting, with Advanced Services. If you go beyond the basic Reporting in the product, you will have to move up. YOu also have Service Broker. But, you will not have Analysis Services (no data warehousing) or SSIS (no ETL). If you need either of these features, you have to go to Developer.
You will also not have some of the BI features, as the Express Manager is missing many of the bits in the full SQL Management Studio and BI Developer. If you need these, you will need SQL Server Developer.