views:

2329

answers:

5

I plan on installing Multiple Instances of MS SQL EXPRESS on my Development Server.

I am hoping this will let me get around the limitations of SQL EXPRESS:

  • 1 GB of RAM,
  • 1 CPU
  • Database size max 4 GB

[I understand and wish that I could afford a full licence version of SQL Server.]

So, would this work? Would each instance have their own independent limitations?

+1  A: 

if you can het this done every instance will behave and run under the same limitations, also you will need to configure the ports since each instance will attempt to listen into the same port.

Oscar Cabrero
Each instance will have a unique name Box\Instance1 Box\Instance2 etcWill they still need to be assigned to different ports?
Harry
Default instances will attempt to listen on TCP/1433. However, you can only have one default instance installed on a server. Named instances, by default, will use dynamic port assignment. You can set the ports statically, but that's not the default.
K. Brian Kelley
+2  A: 

If you have an MSDN subscription then you can install the Development version and I don't believe that has any restrictions...of course it's for development purposes only.

You can purchase SQL Server Developer Edition from Microsoft at this link...it's $50

http://store.microsoft.com/microsoft/SQL-Server-2008-Developer-Edition/product/C5EA00C9?WT.mc_id=productinfocenter

Michael Prewecki
Aye this would be nice! Seriously considering applying for bizspark
Harry
Oh ok, wasn't aware of this developer edition. Thanks for the tip. I will check it out
Harry
Interesting... They are now out of Stock! I wonder if this is due to this tread? LOL
Harry
I ended up joining BizSpark. Great initiative by MS!Thanks for supporting startups!
Harry
A: 

Since it is a development server, I would second the recommendation to go with a copy of Developer Edition. Developer Edition is a specially licensed version of Enterprise Edition which allows you to run it on operating system versions where Enterprise Edition would not normally be allowed to run. The catch is it an only be used for development. At $50, it's well worth the cost.

The problem with running multiple instances is you face the prospect of resource contention for CPU and memory between the instances. You can throttle the memory for each instance and things of that sort, but if you have the option, going with the Developer Edition instance will be simpler and easier to manage.

K. Brian Kelley
+1  A: 

The answer to your question is yes.

All instances will have they own independant limitations.

Problems that you will face are:

  • Obvious performance issue.
  • OS will decide which processor they will use, and there is a good chance that they will all use the same one. You need to try that.
  • Servers need to listen on separete ports
  • Separate master databases, separate coolations, no easy cros database queries
dmajkic
A: 

The problem is that by design, an SQL Server will take as much memory as it can (the larger it's cache the better it's performance will be) and as such, running 4 SQL Servers will simply fight for your ram (1gig is no where near enough.)

That said, the maximum database size is 4 gig, but unless your dealing with images you'll be surprised just how much that is.

We used SQL express and it was fine for what we were using it for (10 user client/server application), plenty of SQL and plenty of queries every second. I would recommend using the express version, and looking into a better one in the future.

FYI: Microsoft Small business server (SBS) comes with a workstation version of SQL Server, plus exchange which means it is EXTREMELY cost effective for a starting business.

Also if your idea is good, you should look at the microsoft programs for new companies (It used to be called empower, it has a new name now...) they are really really good in terms of software, especially server software.

Spence
He said he was looking for a development server option not a production server option but SBS is a very good choice provided you can live with it being your domain controller too.
Michael Prewecki