Unless we don't need anything specific, we can just go for the basic type:Įventually, we'll be prompted with the Installation Complete window, which will also give us some useful info, including the database instance name and a default connection string ready for a connection test:įrom here, we can click the Install SSMS button and download SQL Server Management Studio, a tool that we can use to create our fist sample database and also a dedicated user that can access it. The installation process is pretty straightforward. Needless to say, we need to install it on a machine that is reachable from our web server via a Local Area Network ( LAN) or within the web server itself, although this is definitely not a recommended choice: both IIS and SQL Server are resource-intensive, hence it could be advisable to keep them in two separate environments.
In this post we'll see how to properly setup and configure an instance of Microsoft SQL Server 2017 Express Edition, aka MSSQL2017, which can be downloaded for free from this Microsoft page. Having read and said all that, here come my 2 cents: although LocalDB is great, for a production machine I would strongly recommend using a standard, full-fledged and service-based instance of SQL Server: a s for the chosen edition, we can either go for Express, Web, Standard, or Enterprise, depending on what we need and/or can afford.
Preinstalled with AWS Systems Manager, AWS CloudFormation, AWS Tools for Windows PowerShell, and various drivers to make your management easier.Built, updated, and fully-patched by AWS for SQL Server running on EC2.