If you want to add a stored procedure to the Person schema, you’ll want to add a folder to the Person structure and name it Stored Procedures. This is simply because in the database the Person schema has no stored procedures. Note that the HumanResources schema has a folder for Stored Procedures, while Person does not. Under these are folders for all of the present object types. In the image below, you can see I expanded two of the schemas, HumanResources and Person. Each folder at the top level represents a Schema, or database level object such as Database Triggers. When it’s done just click finish, and you’ll see the new structure in the Solution Explorer. As I said though, my experience has been Schema\Object Type is the easiest to work with. If you are a hard core DBA you might find Object Type more comfortable, since it’s closer to the Object Explorer in SSMS. You can also organize by just Schema, or just Object Type. I wouldn’t recommend this option, as it will quickly get difficult to find the files you need to edit. You can also pick None, which will put all the SQL files in the root of the project. I personally prefer the default of Schema\Object Type. The one thing to note is the Folder structure drop down. Import settings can be left at their defaults. Target Project is disabled, since it’s in the context of the current project. Use the New Connection button to setup a connection to your database (here I picked Adventure Works 2012). The Import Database is similar to the one from the 2010 database projects, but simplified. Start by right clicking on the project (not the solution) and pick Import, Database.
In this entry we’ll see how to import an existing database into the project. In the previous post we saw how to create a new project using SSDT.
0 kommentar(er)
