Do you use SQL Server? Are you losing track of what's going on when you run your code on SQL Server? Then you must know of this tool called SQL Profiler.
SQL Profiler uses an integrated SQL parser to build statistics on the most accessed tables and columns and can generate SQL index creation files. Other information is also gathered and displayed, such as the request time for a single request, for a class of request, and for all the requests. Sorting may be done on these views to detect database problems efficiently.
This tool can be very useful when you have a big volume of queries that you need to analyze not one by one (meaning that the specific time isn't that much of interest), but rather when you want to know what "group" of queries is taking a lot of time, such as queries on the same tables and columns but with different query values.
You can use this as an audit tool as well particular when you want to watch the traffic on your sql server.
How do I get SQL Profiler?
SQL Profiler is one of the standard suite of client tools that are distributed with SQL Server 2000. You can install these tools from the SQL Server setup disk; they are a part of the main SQL Server setup, but you don't have to install SQL Server to install the client tools.
After installing the client tools, you can launch SQL Profiler by selecting Start, Programs, Microsoft SQL Server, Profiler. SQL Profiler will open without apparently doing anything. It's waiting for you to define a trace: a set of characteristics that tell it what to keep an eye on. That is what it does, keeps an eye on what's going on in the database.
Yesterday I tried using a couple of RevolveScaleR functions -- RxSqlServerData and RxImport.in Rstudio. These are my learnings as part of ...
I have been in hibernation for too long now. I have changed jobs and now hjaving an opportunity to work on SAS code after nearly 11 years. ...
The following features cannot be saved in macro-free workbooks VB Project To save a file with these features, click no, and then choose ...