Showing posts with label reading. Show all posts
Showing posts with label reading. Show all posts

Monday, March 12, 2012

Remote profiling

I keep reading how you are supposed to run traces from a remote server, but I
don't see any way to do that using sp_trace_create. Can this only be done by
running SQL Profiler from the remove server?
Thanks,
Brandon
Where do you see this advice and what exactly do you mean by "run traces
from a remote server"? sp_trace_create like any sp will be run on the
server you are connected to regardless of where the client app is that
issued the statement. The preferred way to create the trace is to have it
output directly to a file on a locally attached drive (not a network share).
It does not matter where you start the trace from just where the file will
be. If you run Profiler this is different. It is a client app but requires
the trace information be sent back to the client for display and processing.
This can be very expensive in some cases and should only be used on light
loads or small periods of time. You can always take the file produced from
sp_trace_create and load it into profiler anywhere you like with no impact
on the server other than what it takes to copy the file to the client.
Andrew J. Kelly SQL MVP
"Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>I keep reading how you are supposed to run traces from a remote server, but
>I
> don't see any way to do that using sp_trace_create. Can this only be done
> by
> running SQL Profiler from the remove server?
> Thanks,
> Brandon
|||Is it possible to load the profiler client app on a system running SQL 2005
Express?
Thanks
Clyde
"Andrew J. Kelly" wrote:

> Where do you see this advice and what exactly do you mean by "run traces
> from a remote server"? sp_trace_create like any sp will be run on the
> server you are connected to regardless of where the client app is that
> issued the statement. The preferred way to create the trace is to have it
> output directly to a file on a locally attached drive (not a network share).
> It does not matter where you start the trace from just where the file will
> be. If you run Profiler this is different. It is a client app but requires
> the trace information be sent back to the client for display and processing.
> This can be very expensive in some cases and should only be used on light
> loads or small periods of time. You can always take the file produced from
> sp_trace_create and load it into profiler anywhere you like with no impact
> on the server other than what it takes to copy the file to the client.
> --
> Andrew J. Kelly SQL MVP
>
> "Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
> news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>
>

Saturday, February 25, 2012

Remote Connection to SQL Server Express

Hi ,

After reading the SQLexpress weblog , I tried the solution and its still not working

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

The client computer gives me this:
Run-Time error -2147217843 (80040e4d)

Log-in failed for user "Kit\Guest"

The connection string in the ADO object in my testing VB6 program is:

my_connection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=kit;Initial Catalog=AdelaideMushroom;Data Source=KIT\SQLEXPRESS"

I am confused with the error massage as my conncection string is set to connect on UserID = Kit

I am not sure what is gone wrong. The same VB6 program runs perfectly on host machine

I am not sure is there anything to do with SQL Config. Manager's SQL server 2005 service's Log-ON setting:

Log On as - Build-in account: Network service

could Anyone who managed to get remote connection work give me some advise? I am desperate. have read that weblog many times and do not know how to get it work


If you are using WIndows Authentication (with specifying the SSPI part in the connection string) UserId will be ignored, because this is the SQL Server Authentication. The problem that you are experiencing with the Guets user is based on the setting that you probably have Windows XP and enabled the "Simply File and Printer Sharing". You can disable that by navigating through Explorer > Tools > Folder Options > View > Scroll down to the end , deactivate "Simple file sharing"

HTH, jens Suessmeyer.

http://www.sqlserver2005.de|||

Thank you for the answer

I will give it a try when I get back to office tomorrow

|||

Sorry.... but I still get the same error message

I have firewall of host computer disabled, it connects ok with this command

C:\Documents and Settings\Kit>sqlcmd -E -S KIT\SQLEXPRESS,2301

I have simple file sharing disabled, I no longer see any folder visible on my computer (execept printer & fax and Scheduled Tasks) in Map Network drive.

Seems that the client computer has found KIT\SQLEXPRESS but somehow the host computer direct the client computer to Kit\Guest

The host computer User Account shows there are 3 accounts: KIT (myself), SQLDEBUGGER and Guest. I cannot get rid of Guest tough

I've tried turn firewall off on both computer. Same result

Any idea ?