SQL Server understands Management Studio

1. Optimize the function of a variety of tools

There are two tools in previous versions of SQL Server: Graphical administrative Tools (Enterprise Manager) and Transact SQL Editor (Query Analyzer). There is a problem with such two tools, the need to develop SQL Server and the need to manage SQL Server, sometimes two tasks need to be done simultaneously, so it is necessary to switch between two tools. In SQL Server Management Studio, the Enterprise Manager and Query Analyzer two tools are combined in one interface, which enables you to write Transact SQL while the server is graphically managed. The Object Browser in SQL Server Management Studio combines the Object Browser of query Analyzer with the server-number view of Enterprise Manager to browse all servers. In addition, the Object Browser provides a workspace similar to Query Analyzer, and features similar language parsers and display statistics in the workspace. You can now use the Wizards and property pages to work with objects under the same tool while writing queries and scripts.

The SQL Server Management Studio interface has a registered server window that can handle multiple servers at the same time. Although Enterprise Manager also has this capability, SQL Server Management Studio can not only register the server, but also register Analysis Services, Reporting Services, SQL Server Integrated Services, and mobile SQL. This enables you to gain a view of the entire enterprise or to focus on specific entities or objects of interest.

Working with projects

2. Use of projects and programmes

If you have used Visual Studio, you will not be unfamiliar with the concepts of projects and scenarios. In nutshell, a project can combine a set of files to be accessed as a group. A series of items that make up a group, so that you can drill down on items just as an OLAP user would drill down into a data element in their own interest. Projects include. Sql.mdx.xmla and. DMX Scripts. Alternatively, you can add additional files (such as XML or CSV files) to your project. So the project itself is an object that can be drilled. The steps to create a new project are as follows:

Click on File | To create a new | project.

Select the type of project you want to create (SQL Server script, parsing service script, or SQL move script).

Name the project or scenario that you created.

Select the storage path for the file.

Point OK.

You can then define different data sources (if the project you are creating touches more than one database) or add a file that is easily added (just right-click the script folder in Solution Explorer and select the item you want to add). If you are prepared beforehand, you can also import the script into the project. (If you cannot find the scenario Explorer in SQL Server Management Studio, you can choose to view the | scenario Explorer or press [Ctrl]+[alt]+l.) )

3. Help data Analyst

Thank SQL Server Management Studio for integrating OLAP tools as the best tool for working with the cube. The Object Browser allows the user to access the profiling service object for graphical management of the cube. Users can also write and execute MDX, DMX, and XMLA statements in the editing window, using the same tool and even OLTP and OLAP queries in the same object.

4. Line number Display

When using Query Analyzer, how many times do you have to count from the first line to find the wrong statement? SQL Server Management Studio can display line numbers in the encoding editor, which is useful when parsing encodings to find error rows or typos. This feature is not enabled by default. To enable, follow these steps:

Select Tools | options.

In the expand Selection, record the text editor, and then select all languages.

On the right side of the property window, select the line number below the display heading.

The line number appears to have a feature. If there are batch statements in the script (start, end, or make statements), the row numbers within the block are recalculated in the resulting page (for example, the calculation starts at 1).

Troubleshooting

5. Easy to find error

SQL Server Management Studio retains one of the features in query analysis: You can connect directly to the wrong part of the script by using an error message in the Messages window. Note that if more than one batch statement is included in the script, the line number displayed in the error message may not match the actual line number. Just double click the error message in the red text in the message window to find the statement that caused it. This action will highlight the problematic rows in the script body. (You may also be willing to use the profiling feature to clear the syntax error before running the script.)