Database Deployment in Visual Studio

A software project should have a database. You can use SQL or no-SQL database. You choose SQL when you work with structured data that should have specific constraint and schema. You choose no-SQL if you prefer a simple and high-performance data access. Visual Studio officially support both databases. On this article, we discuss what database option that we have and how to choose the correct option.

SQL Database

You have a lot of options to deploy SQL-based database. We will focus on two main approaches in this post.

  • SQL database that can be embedded in the application.
    • If you build a desktop software that run on top of Windows. You can use Microsoft Access.
    • If you build a web that run on top of Windows based hosting. You can use SQL Compact Edition. You can install the extension on the visual studio marketplace
  • SQL Database that should deployed separately in the application.

You can deploy both database to Microsoft Azure and your on-premises environment. You can do the deployment process through SQL Server Management Studio or Visual Studio Server explorer or publish profile.

No SQL Database

Unfortunately, there is no built-in support for No SQL Database. This is because the NO SQL database is simple enough to install and to implement by using NuGet package manager.

blog comments powered by Disqus

Topics Highlights

About @ridife

This blog will be dedicated to integrate a knowledge between academic and industry need in the Software Engineering, DevOps, Cloud Computing and Microsoft 365 platform. Enjoy this blog and let's get in touch in any social media.

Xbox

Month List

Visitor