Personally, if I could have worked on any other product team besides ASP. Internally, SQL Server is an amazingly complex piece of software, but programming and using it is quite easy. Understanding some of this complexity is important because, as you'll find, the database is often the bottleneck in your application and the more you know about the internals of SQL Server the more you can do to avoid those problems.
How much time do you spend analyzing how your application uses its database resources? For developers, the most common answer is not very much. Typically most performance problems are addressed in one of two ways: by adding new hardware or by tuning the code that runs the application. Most developers prefer to tune the code, but sometimes it actually can be more effective to just add new hardware. It should be noted, however, that performance problems can sometimes be worsened by adding new hardware before analyzing for bottlenecks.
If a bottleneck is in the software, fast performing hardware can queue requests faster, making the bottleneck worse. The best approach, as always, is to analyze bottlenecks hardware or software before doing anything. Being a developer, I prefer to sling some code first, before taking the hardware approach. Once that decision is made, it is usually a matter of doing some basic profiling of the application using Application Center Test and identifying where in the application performance is poor.
Once the problem areas are identified, the next step should be to use SQL Server Profiler to inspect how the application uses database resources. When it comes to writing high-performance Web applications, there is a performance truism: if your application performs any cross-process communication database, Web services, remote object invocation it's a better use of your time to either optimize those communications or to remove them entirely before attempting to optimize other code within your application.
For database optimization, my general rule of thumb is if the application is going to the database more than once or twice on a given request or making a single Web service call , there must be a very good reason for it because those roundtrips are most often the cause of poorly performing applications. My team at Telligent has just spent the past three weeks tuning our Community Server for forums. We made nearly 40 performance-related changes, of which 75 percent were in the database while the other 25 percent were directly related to code changes to either reduce or optimize the time spent in the database.
The caching features of ASP. NET are one of the best tools for reducing database round-trips. If you are using SQL Server you've already got a great set of tools, the Profiler and Query Analyzer, for understanding how your application is using the database. This book is one of my favorite references—my own copy is highlighted and coffee stained.
Hopefully your copy will enjoy a similarly useful existence. Reviewing logs or trace files generated by your application is invaluable for understanding how your app is being used. For example, for Web developers it is common to review IIS logs to understand app use.
Within Community Server there is a built-in exception handler to trace all exceptions generated; later, we can review these logs and quickly get a good idea of the problem areas. You can glean important information such as how many queries your database is executing, how much time those queries are taking, which database is executing which query, and so on.
Figure 1 shows a profiler session with the database used on the asp. You can see several captured SQL traces, which show stored procedures for weblogs. There is much passionate debate about using stored procedures.
One of the benefits of stored procedures in enterprise applications is encapsulation and abstraction. If an application is using dynamic SQL SQL text that is being generated on the fly , the application is typically more challenging to tune.
Tuning dynamic SQL requires recompiling the application. Stored procedures, on the other hand, encapsulate their functionality and can be modified without affecting the public signature. Management Studio query analyzer jika di versi SQL server 3. Before writing codes in SQL, it is important to understand the various components in Management Studio.
This course will introduce you to tools for integration services, SQL Server Profiler as well as server management tools. You will be taken through various options to personalize Management Studio using smart indenting. Did you know that the Object Explorer can display up to 65, objects at the same time?
It is impossible to code in the SQL environment without the use of its tools. By completing this course, you will familiarize yourself will all the available tools and learn how to use them. If you want to learn how to switch to full-screen mode, connect to other servers or use SQL commands to execute scripts and operating system commands, then you should complete this course.
This course explains the methods for creating new queries, managing multiple query windows and executing codes in a query editor. It illustrates the techniques for creating data manipulation language scripts and data definition language scripts in order to execute procedures.
Dynamics SL More Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue.
0コメント