dbTalk Databases Forums  

remove loginname column from existing trace file?

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss remove loginname column from existing trace file? in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
geekyguy
 
Posts: n/a

Default remove loginname column from existing trace file? - 08-31-2008 , 03:58 PM






Hi All:

I created a trace file, and when I ran tuning advisor many of the queries of
interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor to
run the trace under the connected user (currently with dbo privileges)? If
anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs even
better <g>.


Reply With Quote
  #2  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM






I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #3  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #4  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #5  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #6  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #7  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #8  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #9  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
  #10  
Old   
Andrew J. Kelly
 
Posts: n/a

Default Re: remove loginname column from existing trace file? - 09-01-2008 , 08:47 AM



I don't use the tuning advisor much so I can't say if what you are asking
will work or not. But you can load the trace into profiler and then deselect
any column you wish (well mostly) and save that to a trace file which will
then not include those columns.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"geekyguy" <geeky (AT) guy (DOT) com> wrote

Quote:
Hi All:

I created a trace file, and when I ran tuning advisor many of the queries
of interest couldn't be optimized because the user didn't have "showplan"
privileges.

Is it possible to remove the login name column to "force" tuning advisor
to run the trace under the connected user (currently with dbo privileges)?
If anyone could provide a step-by-step I would greatly appreciate it.

If it's possible to do this through the profiler or tuning advisor GUIs
even better <g>.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.