October 2006 Blog Posts
Do you ever need to connect to the console of a server? Are you too lazy to go to the server to do it? If so, then check this out from a cmd window:
mstsc /v:serverName /console
I almost never need to connect to the console as most everything that I need to do can be accomplished with the SQL Server tools and the use of Terminal Services/Remote Desktop. But this will come in handy when two other people are already connected to the server via RDP. Now a third person can connect!
We've been having performance problems on a new 64-bit SQL Server 2005 cluster in our test environment. We opened a ticket with Microsoft to assist us with this.
After modifying several things, the only thing that was slow was Management Studio. On both nodes of this cluster, it would take about 3-5 minutes to load Management Studio. The first MS engineer suggested that we add the nosplash switch to the Management Studio shortcut, like this:
This did not increase performance at all on either node. The second MS engineer suggested that we uncheck two options in Internet Explorer's Advanced Security settings. ...
For those of you who have been using SQL Profiler 2005 for a while, you probably are already aware of this. We've been using SQL Server 2005 for a few months now, but I hadn't touched SQL Profiler 2005 very much yet. Today I had to run a trace to check if any of the queries in our performance environment were taking too long. I always save the trace data to a table, so that I can easily run queries against it. Here is my typical query:
SELECT TOP 100 Duration, TextData
WHERE TextData IS NOT NULL
ORDER BY Duration DESC