Which windows server 2008 edition for a DB server - operating-system

We are uprading our servers and we're going to have 3 servers - 1 db server and 2 frontend web servers.
For the web servers we'll use 2008 Web edition but we can't decide which edition to use for the db.
At first we were thinking of using Standard edition but with our host it works out 10 times more expensive per month than the Web edition.
Our third option is to use Data center edition which is only cost 5 times more than the Web edition.
Can we and should we run a SQL 2008 on Windows Server Web edition? If not which edition should we choose?
Thanks.

Minimum requirements for all versions of SQL 2008 are here.
Server 2008 Web is listed as a supported OS, so you should be fine.
EDIT: I should clarify that it's possible to run SQL 2008 on Web Edition of windows server, but I'm not sure of what the limitations of doing so are. Server Web has more limitations than Server Standard, but I'm not sure what they are - be it hardware related or whatnot.

Related

mongodb on windows 10 without windows server 2008?

I'd like to install MongoDB Community Edition on my computer, which has the 64-bit Windows 10 Home OS, but the system requirements say I need Windows Server 2008 to do it.
I don't think my computer has Windows Server 2008. Is there any way around this? For example, would it work for small-scale databases, or is it totally incompatible without Windows Server 2008?
If I absolutely can't use MongoDB, is there another non-relational database that would work with my system? (It would have to be free.)
I admit that the download site is a bit confusing.
But you can simply download the MSI and install it on your Windows 10 machine. A Windows Server version is not required for the community edition.
Disclaimer: I have it on a Pro (Windows 7 and 10, without Windows 2008 or any other server) edition, not on a Home edition, but I'm pretty sure that it will work in the local machine context)

SQL Server 2008 R2 Express: Management Tools Missing from Feature Selection

I am trying to install SQL Server 2008 R2 Express with the SQL Server Management Studio.
However, the Management Tools feature does not seem to be selectable. The screen-shot below shows which Features are available for me to select:
I have made sure that the SQL Server 2008 R2 Management Objects was installed!
I have tried both answered methods at Can't install SQL Server 2008 R2 management tool (complete) and they both do not seem to work for me, I still do not see Management Tools. Upgrading the Edition under the Maintenance section and Uninstalling/Re-installing the SQL Server had no additional effects. The files I am trying to work with to get this to work are:
SQLEXPR_x64_ENU.exe - This is Service Pack 3
SQLManagementStudio_x64_ENU.exe - The file name fooled me, since there is no management studio feature selection!
The question is, why does Microsoft makes it so difficult?
I am using a Windows 7, 64-bit machine. Any help would be greatly appreciated.
You should separately download Microsoft® SQL Server® 2008 Management Studio Express from Microsoft at
http://www.microsoft.com/en-us/download/details.aspx?id=7593
SQLEXPRADV_x64_ENU.exe contains everything and is the best choice for new installs.

instance servername sql server 2012

Hello I have installed management studio 2005(x64) alse I have microsoft sql server 2012 in my pc. But cant connect server due to dont know server name. (if sql server 2008 express were in my pc, default servername would be "./sqlexpress")
How can I connect server in my own pc ? And also I wanted to know;
Should I use another management studio ? can there be a problem use ms2005 with sqlserver 2012 ? Do you recemmond other studio ? (with exp. reason please)
Thank you anyone who just feel to help.
At least one of them must be a named instance. So, open the SQL Server 2012 version of SQL Server Configuration Manager, and see what the services say (and make sure the one you want to connect to is started - you can right-click to do so). Mine are all named instances:
So, if I wanted to connect to the SQL Server 2008 SP3 instance, I would use any of the following to connect:
.\SQL2008SP3
LOCALHOST\SQL2008SP3
(local)\SQL2008SP3
YOURMACHINENAME\SQL2008SP3
127.0.0.1\SQL2008SP3
The exception is if the subtext has (MSSQLSERVER) - this is a default instance rather than a named instance. In that case you would just connect to YOURMACHINENAME or ..
Also, no, you should not use Management Studio 2005 to manage SQL Server 2012 instances. In fact I think the above Configuration Manager won't show your 2012 instance. So before you do anything, you should uninstall the 2005 version of Management Studio, and go get the 2012 SP2 version here:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Click Download, the file you want is SQLManagementStudio_x64_ENU.exe. The nice thing about this version in 2012 SP1 is that it's the first version of SSMS Express that is actually fully functional and license free. Previously you had to live with limitations like no SQL Server Agent management, well those restrictions are now all gone.
(When you instal the client tools, this should also give you a new version of Configuration Manager, if your previous installation of SQL Server 2012 did not provide that for some reason.)

Install SQL Server 2000 from Install Shield 2009 Premier

I have a basic MSI project in InstallShield 2009 Premier. I have some files(dlls, exes) to be copied, no problem. But what I need to install SQL Server 2000 in addition to this. What I did during development time was to install SQL Server 2000 before development(C#.net). I saw re-distributable "Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) SP3a" (need to be downloaded). But would the installation of this re-distributable do the same job as SQL Server 2000?
Any information about installing "SQL Server 2000" from InstallShield... ?
Same question for installation of "Crystal Reports 2007".
If I am understanding your question correctly, adding SQL Server (or Crystal Reports) as a Redistributable should accomplish the same objective, as long as you choose the minimum-required version of SQL server that your application needs.

Best Virtual Development Platform for .NET 3.5 Development

I have basically succumbed to the fact that if you are a hardcore computer user, you will have to reimage your computer every few months because something bad happened. Because of this, I bought imaging software and then really got into imaging. I am now ready to move my development environment completely into a virtual machine so that I can test sites on IIS as though I am on a dev network (and backup these images easily).
The question is, what is the best virtual development platform for a 4 gb laptop? A virtual Vista Business with 3 gb of ram, windows XP sp3 with 3 gb of ram, or Windows Server 2003 with 3 gb of usable ram.
Tools I will need to install:
*sql server 2005 dev edition
*vs 2008 sp1
*tools for silverlight
*and multiple other smaller testing tools
I have tried the following combinations:
Windows XP SP3 on Virtual Server
2005 R2
Windows Vista Business
x64 on Virtual Server 2005 R2
Windows XP on Virtual PC 2007
Windows 2003 on Virtual Server 2005
R2
Windows XP on VMWare Fusion
and the Virtual Server installations where either local or hosted on a server and they all ran fine and about the same speed.
The VMWare Fusion Virtual Machine running under OS X is (seat of the pants) significantly faster than the others. I haven't tested VMWare on Windows to see if it is VMWare or the Hardware making the difference, but it's something worth looking into.
Server 2008, converted to a workstation.
Nothing compares IMO, I've loaded 3 Different OS's in the last 3 months, and I'm set on Server 2008.
I think the biggest question (from my standpoint) is whether or not you'll be doing development (like SharePoint) that requires a server platform. If you anticipate a lot of SharePoint development (or perhaps Exchange, or BizTalk, or another product that requires development be done on a server platform), then go with Windows Server 2003. If not, then I'd probably choose XP, though Vista isn't a bad development platform.
I personally prefer developing on a server platform - however, that opinion might shift if I was developing any sort of WinForms applications, since it would more correctly represent the OS family for the target audience.
I did notice a slight performance decrease going from Server 2003 to Server 2008 that I was not expecting, but that might be more from doing an in-place upgrade instead of starting clean.
From the options you gave, I would personally go with W2k3. You can really trim a server OS down to run lightning-fast, especially when you don't have or get rid of the MS "eye candy".