saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
Mitra
There is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra
|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra
sql

saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
MitraThere is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra

saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
MitraThere is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx
.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx
.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra

Save As Template?

In Enterprise Manager when I bring up Trigger Properties there is an active button titled "Save as Template". But when I switch to an existing trigger the button is disabled. Oddly, the Help file for the dialog box doesn't even mention this button.

Anybody know what this does, how it works, or why it would be usefull? Any references to The Holy Book would be helpfull.It looks like an EM trigger template...of which you can have 1...since mine is now hosed across several servers/instances...|||You can only have one template across all tables and databases for Updates, Inserts, and Deletes? How useless. No wonder they didn't bother mentioning it in Books Online.

Anybody out there ever modified the trigger template?|||Hell...go in and try it...it's not a database object...

What's Em good for...absolutley nothin...say it again...War, what it good for, absoultley nothin...say it again...

oops.....gotta watch those flash backs....|||Yup, I just hosed mine (good thing I try not to use triggers, needless to say create them using EM ;) )|||Originally posted by blindman
In Enterprise Manager when I bring up Trigger Properties there is an active button titled "Save as Template". But when I switch to an existing trigger the button is disabled. Oddly, the Help file for the dialog box doesn't even mention this button.

Anybody know what this does, how it works, or why it would be usefull? Any references to The Holy Book would be helpfull.

Hey BM, since when did you start using EM. I acknowledge , the holy book does not cover EM very well ...

But why to use EM when you can do the same using QA ... did you know ... QA has a save as template option as well ?|||QA - the Holy Tool !!!|||Originally posted by Enigma
Hey BM, since when did you start using EM. I acknowledge , the holy book does not cover EM very well ...

But why to use EM when you can do the same using QA ... did you know ... QA has a save as template option as well ?

Nice shoot... ;)|||Don't make me get up out of this chair....

And yes...I love using QA templates...

anyone seen codesmith though?|||Well in my view :-
EM -- SQL for Dummies|||Originally posted by Brett Kaiser
Don't make me get up out of this chair....

And yes...I love using QA templates...

anyone seen codesmith though?

[Brett Falls trying to get out of his chair]

You are glued to that DBA's chair BK .. dont try to get up :)

[/Brett Falls trying to get out of his chair]

Codesmith ... hmm .. not used it till now .. will try do download and use it once I get out from this Client Office ... damn ... here I need permission to install anyting on my PC.|||I frequently use EM for tweaking existing code.

I like EM, after especially after having had to use Sybase's management interface years ago. Now that was crappy.

...and for that matter I use triggers when they make the coding easier or more robust as well.|||Originally posted by blindman
I frequently use EM for tweaking existing code.

I like EM, after especially after having had to use Sybase's management interface years ago. Now that was crappy...

Yeah? Try SQLPlus for Oracle...

Better yet, use SPUFI on the maijnframe....|||You think that's tough? Back in my day we created enterprise-wide datawarehouse solutions using nothing but Windows Cardfile, Calculator, and a handfull of Post-It notes!

...and we LIKED 'em, Sonny!|||To use or not to use, - personal preference, not a dogma ;)