Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Other SQL Server Topics (2005)
 SQL Profiler issue!

Author  Topic 

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-20 : 16:32:24
Hi,

In the company that I work we have SQL 2005 enterprise edition installed and I am logging into it through remote desktop.

Now, I am trying to have a trace on the server running even if I logout from my session but it does not work? Every time I have to close the session I have to stop the trace.
Is there any way I can make it work?

BTW I tried to have client tools on my PC but it says that my computer does not meet the requirements. Funny, I have processor 3.0 MHz with 1GB RAM.

Help out please?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-01-20 : 19:46:20
Well you should never run SQL Profiler on the actual database server, but to answer your question you just need to disconnect from your RDP session and not logoff.

You probably are attempting to install the Enterprise Edition engine on your desktop, which isn't allowed. Just install the client tools, or better yet install Developer Edition.

1GB of memory is pretty small these days, you may want to consider at least doubling that.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-21 : 03:18:24
Hi Tara, thanks for the info for disconnecting, it works, but could you please let me know why it is not good to run it on the db server, because I can not install it on my PC (client tools), I tried!!!!).

What else can I do, Developer Edition?
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-01-21 : 03:22:28
You are using CPU /Disk / resources on the server, if you run it there, which slows the server down significantly. I suppose the act of monitoring on the server itself also means that the figures are not accurate - if the disk is busy logging the profiler data it can't be doing its SQL work at the same time

Hence it is recommended to run it on a different machine (which can connect to the SQL box)

What problem are you having installing on your PC?
Go to Top of Page

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-21 : 08:43:43
Thanks Kristen.

It installs the Setup support files (on the first step) and then I reach to the point of checking system compatibility and there I receive this error.

SQL Server Edition Operating System Compatibility (Warning)
Messages
SQL Server Edition Operating System Compatibility

Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.


Anyway I click next and I reach Feature selection, where I choose
Client components, documentations etc....

Then the progress bar starts and error is on the MSXML6
and on Workstation, Components, Books etc...

So still I do not have anything except books and tutorials in the end for SQL 2005.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-01-21 : 09:25:24
OK, I've not done a Client Tools only install on SQL 2005, do not sure how it works.

Sounds like what you did was correct but there is some missing piece, or maybe you don't have Admin permissions?
Go to Top of Page

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-21 : 11:01:48
first time as welll and I will have to digin into book online and try to find solution.

Thanks a lot,

I have another question for the developers but I will post it in the new topic.
Go to Top of Page

Transact Charlie
Master Smack Fu Yak Hacker

3451 Posts

Posted - 2010-01-21 : 11:21:59
Not sure if this will help you or not but the performance impact of a server side trace isn't all that bad as long as you aren't logging details to a table in the database or saving files on your working store.

I recently had to set up some server side tracing for deadlock issues and I found this set of tools quite helpful.

You have to be careful and not leave the traces running though so you may want to reconsider.

Anyway, here's the link.
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm


Charlie
===============================================================
Msg 3903, Level 16, State 1, Line 1736
The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION
Go to Top of Page

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-21 : 14:33:53
Thanks Charlie,

Well for the logging table in the db, I did create one in each db which is fired by DDL trigger. But anyway, not much is happening since design does not change a lot only the input is fair so the table is really not getting big quickly.

So the only way I can track who changed what in details is with Profiler? So I have to make it running but only for specific task.
Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-01-21 : 15:14:48
Rather use a server-side trace not the profiler GUI. Profiler Gui has some nasty effects on busy servers.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

tomislavg
Yak Posting Veteran

51 Posts

Posted - 2010-01-21 : 15:58:51
Thanks Gail, I am just reading about it and I think I will go that way.

quote:
Originally posted by GilaMonster

Rather use a server-side trace not the profiler GUI. Profiler Gui has some nasty effects on busy servers.

--
Gail Shaw
SQL Server MVP

Go to Top of Page
   

- Advertisement -