You should see the tables that match the data model you created in the first half of the course, as well as a Migrations table, which tracks the migrations you perform each time you type update-database in the Package Manager Console in Visual Studio. Expanding the Tables folder brings up a list of all the tables in this database. We will work with three folders here: DatabaseDiagrams, Tables, and Programmability. Expand this database to see the list of folders within it. We aren’t using them for the course, so let's skip them for now.īeneath those folders are the databases you created on this server specifically, the ones using code-first migrations from the first half of this course.
![sql server management studio icons sql server management studio icons](http://i.ytimg.com/vi/TpKcAmaaBts/maxresdefault.jpg)
Within this folder are two additional ones: System Databases and Database Snapshots. We're interested in the Databases folder because it contains all of the databases you’ve created on this server. These, like folders, are also expandable, and expanding a database brings up a list of organizational folders within the database containing the various components with which you may need to interact. Databases appear with a database container icon next to them. The Object Explorer works like a file explorer, breaking your server into simple, folder-based components. Once your server is connected, the Object Explorer will display all relevant information to that connection.
SQL SERVER MANAGEMENT STUDIO ICONS WINDOWS
For now, let’s stick to your local server installation and Windows authentication. We’ll do this later when we set up your Azure server. However, if you’re connecting to an online or network server, you’ll most likely want to select SQL Server Authentication from the dropdown. Then click Connect, and your server connection will be established. For local installs, it will most likely be Windows Authentication, which will default to your Windows login username. Alternatively, you can type in (or paste) the name of the server to which you wish to connect, such as the one in the connection string for your application: SQL Server - connect to server with server name suppliedĪt this point, you may change the authentication type if necessary. However, if nothing appears here, or you need to connect to a different server, you may click. You can select one of these if that is what you desire. You’ll see all of the SQL Server instances of which your SSMS installation is aware. To select a server for the connection, click the Server name dropdown, as shown below. This window can also be brought up by clicking the Connect dropdown in the Object Explorer window and selecting Database Engine: Access the connection window within SSMS When you launch SSMS, you will see the SQL Server connection window: SQL Server - connect to server
![sql server management studio icons sql server management studio icons](https://1.bp.blogspot.com/-a2jVtpynOzA/X1CxtKO-sfI/AAAAAAAAERg/LAtQm-0gGVctuSmOj7vJz-_X7DAdCv46gCLcBGAsYHQ/w1200-h630-p-k-no-nu/Untitled%2Bdesign.png)
You may have completed this during the SSMS install, but in case you skipped over it, we’ll go through adding a server to your SQL Server installation via SSMS now. So get that done, and then let’s get busy connecting to your local server. If you haven’t installed SSMS yet, then now is the time to do it, because you’ll need it the rest of the way. You’ve seen SQL Server Management Studio before, but you probably haven’t had an opportunity to learn how it can help you build, maintain, and manage your relational databases.