ApexSQL Edit Replaces the Need for SQL Server’s Query Analyzer
Another important features of ApexSQL Edit is its ability to easily work with multiple windows open, as shown in the screenshot below.
What you see here is a portion of the active query window. At the top are three tabs. The tab in bold is the active window, and the other two tabs show windows that are currently open, but not active. This makes it very easy to find open windows (unlike Query Analyzer).
When you first type code into a query window, you can input it anyway you like, such as shown below.
While this code works, it is not very attractive. But with ApexSQL Edit’s automatic formatting ability; clean, easy-to-read code is a click away, as shown below.
Notice the little box with the hyphen in it above? If you click this, you can collapse the code, as shown below.
While this example is not very dramatic, it gives you a flavor of what this feature can do for you. This is similar to Visual Studio.NET’s collapsible scripting outlining feature.
Another nifty feature of ApexSQL Edit is the ability to quickly test stored procedures, as shown below.
What I have done above is to select the “Employee Sales by Country” stored procedure in the Schema window, and then asked ApexSQL Edit to run it.
When I do, a window is brought up that allows me to enter values to execute the stored procedure with. Also, I can specify if I want to rollback the code after it is executed, and if I want to see any return values. This features goes a long way to helping you test and debug stored procedures.
This is a very short demo of ApexSQL Edit, and as you can imagine, there are many, many other features that I have left out.
Is ApexSQL Edit for You?
Pages: 1 2