All geek questions in one place

SQL Server Management Studio Solution vs Visual Studio Projects

Almost all of our projects use a web application or winforms, as well as a data access level (class library) and stored procedures / database scripts.

We are looking for a good way to organize solutions and have found several ways:

1) We could have a solution for studio sql server management for all things related to db, and then have a visual studio solution for application-level projects and data access.

2) We could do all this in a visual studio with 3 projects, a sql server project, a web application / winforms project and a data access level project.

3) We could do all this in a visual studio with two projects, an application project for web applications / winforms and a data access level project and just put sql scripts in a directory in the data access level project.

I'm sure there are other ways, but I'm just curious to know how others do this.

+3
source share
3 answers

I successfully did this with Visual Studio Team System Database Database Edition - multi-point network projects with a database project in one solution.

Keep in mind that deploying a database project takes much longer because you usually need test data, and most of the attachments to it are RBAR insert statements. We used to disable the deployment of the database project to the absolutely necessary (usually once or twice a week).

Of course, all this was in TFS for source control

+1
source

SQL Server Management Studio Solution

  • Allow the use of a GUI constructor to create and edit some objects.

Visual Studio Projects

  • TFS , ;
  • IntelliSence
+1

I use Management Studio and some batch files to export / import / store sql in the solution (source controlled too).

Thus, every time there is a change in db, which it exports to the solution, and a special tool is configured to update the ORM proxy classes.

0
source

Source: https://habr.com/ru/post/1724149/

More articles:


All Articles