Gurus,
Running SQL Server 2005 SP2. The SQL Server Browser service but since I am
running on dynamic ports it is not listening on 1434. In fact, looking thru
Configuration Manager I am not able to tell what port it is listening on or
how to change it back to 1434. Any ideas?
--
SpinSQL Browser always listens to 1434. It is the database engine that might be static or dynamic.
Browser is only there to translate between instance name and port number.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Spin" <Spin@.invalid.com> wrote in message news:67rgfkF2or7t6U1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2. The SQL Server Browser service but since I am running on dynamic
> ports it is not listening on 1434. In fact, looking thru Configuration Manager I am not able to
> tell what port it is listening on or how to change it back to 1434. Any ideas?
> --
> Spin
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> SQL Browser always listens to 1434. It is the database engine that might
> be static or dynamic. Browser is only there to translate between instance
> name and port number.
On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
listening on port 1434. SQL Browser service IS running.|||"Spin" <Spin@.invalid.com> wrote in message
news:67ro9qF2q0vlvU1@.mid.individual.net...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
> listening on port 1434. SQL Browser service IS running.
Disregard. I've done some reading and the SQL Browser service listens on a
UDP port, netstat only shows TCP ports on which connections are either
established or the server is listening. I have to figure out what UDP ports
are being listened. This may be a bit more difficult.|||"Spin" <Spin@.invalid.com> wrote in message
news:67rrf3F2q34siU1@.mid.individual.net...
> "Spin" <Spin@.invalid.com> wrote in message
> news:67ro9qF2q0vlvU1@.mid.individual.net...
> Disregard. I've done some reading and the SQL Browser service listens on
> a UDP port, netstat only shows TCP ports on which connections are either
> established or the server is listening. I have to figure out what UDP
> ports are being listened. This may be a bit more difficult.
Using TCPView.exe from Microsoft, I can clearly see now on at least one SQL
Server that the SQL Broswer service is listening on UDP 1434!
Tibor, am I correct in believing that the SQL Browser listening port CANNOT
be changed?|||> Tibor, am I correct in believing that the SQL Browser listening port CANNOT be changed?
Yes, that is the way I understand it. The whole purpose of SQL Browser is to be a fixed port. This
is so that outsiders can query it (that specific port) for the port number for an instance name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Spin" <Spin@.invalid.com> wrote in message news:67rtnuF2qnt8iU1@.mid.individual.net...
> "Spin" <Spin@.invalid.com> wrote in message news:67rrf3F2q34siU1@.mid.individual.net...
>> "Spin" <Spin@.invalid.com> wrote in message news:67ro9qF2q0vlvU1@.mid.individual.net...
>> Disregard. I've done some reading and the SQL Browser service listens on a UDP port, netstat
>> only shows TCP ports on which connections are either established or the server is listening. I
>> have to figure out what UDP ports are being listened. This may be a bit more difficult.
> Using TCPView.exe from Microsoft, I can clearly see now on at least one SQL Server that the SQL
> Broswer service is listening on UDP 1434!
> Tibor, am I correct in believing that the SQL Browser listening port CANNOT be changed?
>
>|||You can use netstat to show UDP ports that are being listened on. Run the
following:
cmd>netstat -ano
One of UDP rows in the result will have port 1434. Find the the PID, and run
tasklist to confirm that the PID is sql browser.
Linchi
"Spin" wrote:
> "Spin" <Spin@.invalid.com> wrote in message
> news:67ro9qF2q0vlvU1@.mid.individual.net...
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> > in message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> > On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
> > listening on port 1434. SQL Browser service IS running.
> Disregard. I've done some reading and the SQL Browser service listens on a
> UDP port, netstat only shows TCP ports on which connections are either
> established or the server is listening. I have to figure out what UDP ports
> are being listened. This may be a bit more difficult.
>
>sql
Showing posts with label gurus. Show all posts
Showing posts with label gurus. Show all posts
Wednesday, March 28, 2012
Monday, March 19, 2012
How to catch io's for tsql execution.
Hi gurus.
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system views.
Thank you for your input.
Gene.
You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system views.
Thank you for your input.
Gene.
You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
How to catch io's for tsql execution.
Hi gurus.
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system views.
Thank you for your input.
Gene.You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system views.
Thank you for your input.
Gene.You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
How to catch io's for tsql execution.
Hi gurus.
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system view
s.
Thank you for your input.
Gene.You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
I want to catch execution statistics like 'reads', 'execution time' for some
reports.
I know I can run it with 'set statistics io on' but it does not effectively
servers the purpose since output can be truncated from sql agent history.
Or I could achiveve it by calling tsql from command line shell, catching
output and parsing it.
Or I can run profiler and catch statistics to table and than browse this
table.
Is there any more elegant and simple way doing it? I was thinking about
executing it and then being able to find execution statistics in system view
s.
Thank you for your input.
Gene.You could set up a server-side trace to a file with a very tight filter of
just the few sprocs you wish to track. The file could be loaded into a
table for historical tracking and analysis.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:A7D159E0-B654-47F3-8CBE-EB374CA2ADDA@.microsoft.com...
> Hi gurus.
> I want to catch execution statistics like 'reads', 'execution time' for
> some
> reports.
> I know I can run it with 'set statistics io on' but it does not
> effectively
> servers the purpose since output can be truncated from sql agent history.
> Or I could achiveve it by calling tsql from command line shell, catching
> output and parsing it.
> Or I can run profiler and catch statistics to table and than browse this
> table.
> Is there any more elegant and simple way doing it? I was thinking about
> executing it and then being able to find execution statistics in system
> views.
> Thank you for your input.
> Gene.
>
Subscribe to:
Posts (Atom)