November 30, 2015 at 10:59 am
Forgive my greenness on the above.. we are trying to understand what it will take to migrate functionality from an existing LAMP based application to something that uses MSSQL on Windows Server...
We are self-hosting an application that will draw it's data from multiple unique customers who will be log shipping to our centralized server. Each customer has a dedicated always on IPSEC connection, and our main box will be receiving one-way replication to our server. There will be a dedicated VMware machine that will be the host of the MSSQL server that is running 2008 Server R2 (server is not on a domain). Each customer's users will login to our webapp via the public internet (currently planning on running IIS on the same box), and the app will connect the MSSQL databases specific to their account.
This is a niche app, so there would not likely be more than 4 or 5 unique customers on this instance, each with perhaps 5-10 web users.
In addition to the above, we would need to administer the databases via SQL Management studio, and there could be 2-3 users connected at the same time to the server.
Am trying to do this as cost effectively as possible... Is something like this an option?
or is the web edition and option? I'm looking to be creative.
November 30, 2015 at 11:55 am
kenny 40254 (11/30/2015)
Forgive my greenness on the above.. we are trying to understand what it will take to migrate functionality from an existing LAMP based application to something that uses MSSQL on Windows Server...We are self-hosting an application that will draw it's data from multiple unique customers who will be log shipping to our centralized server. Each customer has a dedicated always on IPSEC connection, and our main box will be receiving one-way replication to our server. There will be a dedicated VMware machine that will be the host of the MSSQL server that is running 2008 Server R2 (server is not on a domain). Each customer's users will login to our webapp via the public internet (currently planning on running IIS on the same box), and the app will connect the MSSQL databases specific to their account.
This is a niche app, so there would not likely be more than 4 or 5 unique customers on this instance, each with perhaps 5-10 web users.
In addition to the above, we would need to administer the databases via SQL Management studio, and there could be 2-3 users connected at the same time to the server.
Am trying to do this as cost effectively as possible... Is something like this an option?
or is the web edition and option? I'm looking to be creative.
What will be the absolute maximum size of each database? If it will always be < 10GB per database, you can actually get away doing this for free using SQL Server Express edition. Of course, you won't have an SQL Server Agent to schedule jobs with, either.
--Jeff Moden
November 30, 2015 at 11:57 am
I was going to suggest Express Edition too if db sizes allow. If not, then you are probably into Standard Edition and per-core licensing, so then it becomes a matter of how many cores do you need to serve the load successfully.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
November 30, 2015 at 12:04 pm
We need to schedule jobs, so the Express edition is not going to work..
Would this work?
And is this a good price? Right now our server is only 2 core, but the 4 core edition is not too much more $$
November 30, 2015 at 12:07 pm
I would be little hesitant purchasing SQL licenses from ebay, try reputed retailers like CDW, you might get the same price what you see on ebay. There are more details here regarding licensing. Get an estimate from retailer and may be you can check with others here see if you got a good deal . We use Server+CAL licensing, but we are on 2008R2, starting 2012 licensing model has changed quite a bit.
November 30, 2015 at 12:30 pm
kenny 40254 (11/30/2015)
We need to schedule jobs, so the Express edition is not going to work..Would this work?
And is this a good price? Right now our server is only 2 core, but the 4 core edition is not too much more $$
Not sure how small is your business but you can also try https://www.microsoft.com/bizspark/ , they have free licenses for SQL server and Azure
November 30, 2015 at 2:45 pm
Good idea, on BizSpark program... I've applied...
December 2, 2015 at 1:53 am
kenny 40254 (11/30/2015)
We need to schedule jobs, so the Express edition is not going to work..
It is possible to schedule tasks to run without using the SQL Agent task. You can use the Windows Task Scheduler, and make sure that your jobs are stored somewhere safe on the server.
OK, you won't get the same level of reporting detail on the job history. And the security around the jobs is a lot less controlled. But for a cheap fix, it should do the job.
Thomas Rushton
blog: https://thelonedba.wordpress.com
December 3, 2015 at 6:51 am
Following up on Thomas Rushton's suggestion, here are 3 links I've had bookmarked for quite some time for ideas to circumvent the lack of Agent in SQL Express. Haven't tried any of them:
http://spaghettidba.com/2014/01/23/sql-server-agent-in-express-edition/[/url]
http://www.sqlteam.com/article/scheduling-jobs-in-sql-server-express
https://standalonesqlagent.codeplex.com/[/url]
I notice that 2 of these are over 5 years old, but you said you were going to install SQL 2008 for some reason, so maybe one of these will be useful to you. Again, you need to make sure you're OK with the other limits imposed by SQL Express.
Rich
December 19, 2015 at 1:51 pm
@curious, I managed to get into the BizSpark program and it seems that I have access to every imaginable piece of MS software via MSDN. I'm going to download and install: SQL Server 2014 Standard Edition with Service Pack 1 (x64) - DVD (English). What kind of limitations can I expect on this (or how can I find out regarding limitations) with the assumption that I will use this in production.
December 19, 2015 at 2:02 pm
My understanding is that BizSpark gives you licenses that are straight-up what they say they are and don't carry any additional restrictions (other than perhaps the BizSpark duration which is what, 3 years?).
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
December 19, 2015 at 3:35 pm
MSDN subscriptions are for non-production only, unless otherwise specified e.g. 1 production Office license and 1 production Visual Studio license per licensed MSDN user. Another restriction that sometimes is mentioned is that only the licensed MSDN user may install the software, but others may use the software for testing, demonstration, and by extension training purposes. Either way MSDN subscription is not for production use, but Biz Spark is.
Assuming you need a SQL Server instance for each customer:
Cheaper alternative to Standard edition is web edition, which is only offered by service providers (including cloud). If you have enough customers you might be able to buy web edition licenses from Microsoft. Workgroup edition was a cheaper edition for older versions, but not for 2014 if I recall correctly.
With Enterprise edition you can have unlimited VM's as long as you license all the physical cores in the VMware server or cluster.
If you use CAL licensing you should be aware that the number of users connecting is counted at the web application, not at the SQL Server instance. It's not possible to reduce the number of CALs needed by multiplexing connections. If your application is used by external users on the Internet, core licensing is in most cases the only option.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply