February 20, 2017 at 9:55 am
Hey guys, let me say that I am about as new as they come when it comes to SQL and the such. So I have a few quick questions and would like to get a few opinions if I can.
Currently, I develop websites in Visual Studio, create DB files within the project, and use SQL Express on my workstation pc.
Well, its time to get this website published to a local IIS server that is actually in a VM of a Windows 2016 server. Since this website is rather simple, and the db access is rather simple, should I just install SQL Express on the IIS Server and continue to use that? Or, my other option is to create a new VM on the Windows 2016 server and install a full version of Windows SQL Server 2016 and use that.
If, I do the VM route and use a full version of SQL Server. This will pose two more questions. There is no domain in my setup. All these servers and VM servers are all just servers on a workgroup. So, should I just make the SQL Server in the VM a workgroup server? Will there be any connectivity issues between the VM IIS server (no domain) and the VM SQL Server (no domain)?
Back to the original start... mind you... this isnt a very complex website and database. However, I NEED the ability to expand it down the road. Wether that be move the DB file from SQL Express to a full SQL Server or... even later... to an Azure database.
Please any thoughts and opinions?
I personally am just siding on the install of SQL Express on the IIS Server... any downsides to that?
Thank you guys so much....
February 20, 2017 at 10:05 am
andrewhodge - Monday, February 20, 2017 9:55 AMHey guys, let me say that I am about as new as they come when it comes to SQL and the such. So I have a few quick questions and would like to get a few opinions if I can.Currently, I develop websites in Visual Studio, create DB files within the project, and use SQL Express on my workstation pc.
Well, its time to get this website published to a local IIS server that is actually in a VM of a Windows 2016 server. Since this website is rather simple, and the db access is rather simple, should I just install SQL Express on the IIS Server and continue to use that? Or, my other option is to create a new VM on the Windows 2016 server and install a full version of Windows SQL Server 2016 and use that.
If, I do the VM route and use a full version of SQL Server. This will pose two more questions. There is no domain in my setup. All these servers and VM servers are all just servers on a workgroup. So, should I just make the SQL Server in the VM a workgroup server? Will there be any connectivity issues between the VM IIS server (no domain) and the VM SQL Server (no domain)?
Back to the original start... mind you... this isnt a very complex website and database. However, I NEED the ability to expand it down the road. Wether that be move the DB file from SQL Express to a full SQL Server or... even later... to an Azure database.
Please any thoughts and opinions?
I personally am just siding on the install of SQL Express on the IIS Server... any downsides to that?
Thank you guys so much....
With the servers in a workgroup you'll be pretty much forced to use SQL Server authentication for the connection between the web server and the IIS server.
Expanding the workgroup to a domain will be beneficial now but could still be done later down the line, albeit with maybe a little more work to do. Separating the IIS and SQL Servers (even if you leave it on Express edition) will provide a good grounding for the future.
Who will be creating the domain?
Have you registered or at least checked your domain name is available?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 20, 2017 at 10:28 am
Thanks for the quick reply. I will be handling the whole thing... creating the domain if going that route, setting up the servers, etc.
Where I am currently sitting is, I have this pretty loaded server sitting here on my desk. I have a fresh install of windows server 2016, with the Hyper-V role installed.
This is the only "physical" box I have to work with, aside from my workstation of course... but, I would like to get an IIS server up and running, and an SQL server, and, possibly a few other servers/roles.
Instead of just adding the IIS role to this server, I created a vm for the IIS server... thinking I could always move it, shut it down, upgrade to a physical server, or, move it to the cloud...
Same thought process for the SQL Server. Instead of install SQL Server on this box, I created a VM for SQL Server... although I havent actually installed or set it up yet. I dont know whether i really "need" a full SQL Server in a VM, let alone on its own box. So, I was siding with just installing SQL Express on the IIS Server vm and going with that for now... however, I just want to make sure that if I do that, later on, will it be hard to move from that, to a full version of SQL Server, or to the cloud.
Licenses are NOT an issue in any of this... I have full licenses to go just about any route... however, I only have one physical server box...
February 20, 2017 at 10:42 am
andrewhodge - Monday, February 20, 2017 10:28 AMThanks for the quick reply. I will be handling the whole thing... creating the domain if going that route, setting up the servers, etc.Where I am currently sitting is, I have this pretty loaded server sitting here on my desk. I have a fresh install of windows server 2016, with the Hyper-V role installed.
This is the only "physical" box I have to work with, aside from my workstation of course... but, I would like to get an IIS server up and running, and an SQL server, and, possibly a few other servers/roles.
Instead of just adding the IIS role to this server, I created a vm for the IIS server... thinking I could always move it, shut it down, upgrade to a physical server, or, move it to the cloud...
Same thought process for the SQL Server. Instead of install SQL Server on this box, I created a VM for SQL Server... although I havent actually installed or set it up yet. I dont know whether i really "need" a full SQL Server in a VM, let alone on its own box. So, I was siding with just installing SQL Express on the IIS Server vm and going with that for now... however, I just want to make sure that if I do that, later on, will it be hard to move from that, to a full version of SQL Server, or to the cloud.
Licenses are NOT an issue in any of this... I have full licenses to go just about any route... however, I only have one physical server box...
I didn't mean to throw that licensing part in there the way I did. I mean, just because I have the licenses for full versions of this or that... I don't necessarily want to set it up as some full blown complex domain environment just because I can... hope that helps...
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply