I plan to automate a process using about 20 steps and would
like to use SQL Server Agent. I'm finding it difficult to learn how
Agent works. The help files are skimpy and scattered and
leave many questions unanswered.
One thing I've noticed is that Agent does a lot of things behind
the curtain that the user did not request. If I write a script using
TSQL commands like sp_add_job, sp_add_job_step, etc., and
then invoke it via Agent, Agent does things that aren't in my
script. If I ask Agent to generate a script for my job it spits
out a script that includes most of what I ordered, but with
a lot of other boilerplate that I didn't order and some things
like transaction management, that may not have been what
I wanted.
Is all of this documented somewhere? Has someone written
a good book that covers this and gives recommendations on
the best ways to use Agent?
Thanks.
Alan<ameyer2@.yahoo.com> wrote in message
news:1153251901.175708.34630@.s13g2000cwa.googlegroups.com...
>I plan to automate a process using about 20 steps and would
> like to use SQL Server Agent. I'm finding it difficult to learn how
> Agent works. The help files are skimpy and scattered and
> leave many questions unanswered.
> One thing I've noticed is that Agent does a lot of things behind
> the curtain that the user did not request. If I write a script using
> TSQL commands like sp_add_job, sp_add_job_step, etc., and
> then invoke it via Agent, Agent does things that aren't in my
> script. If I ask Agent to generate a script for my job it spits
> out a script that includes most of what I ordered, but with
> a lot of other boilerplate that I didn't order and some things
> like transaction management, that may not have been what
> I wanted.
> Is all of this documented somewhere? Has someone written
> a good book that covers this and gives recommendations on
> the best ways to use Agent?
>
I would build your 20-step process in an SSIS package. Then deploy that
package as a 1-step SQL Agent job.
SSIS has a graphical workflow designer, integrated debugger, rich logging,
etc.
David|||David Browne wrote:
> ...
> I would build your 20-step process in an SSIS package. Then deploy that
> package as a 1-step SQL Agent job.
> SSIS has a graphical workflow designer, integrated debugger, rich logging,
> etc.
> David
Thanks David.
Unfortunately, we're still running SQLServer 2000, and it looks
like we'd have to upgrade our servers to SQL Server 2005 to
use SSIS. That may be more expensive and time consuming
than management would support just for this task.
Agent also has a graphical user interface, though I'm not sure
I wouldn't prefer submitting a script. The big advantage of a
script over a GUI, in my view, is that you can see everything
that happens in one listing, and if you're running multiple servers
you can easily move it to all of them. You can also document
a script with extensive comments.
However it looks like Microsoft really doesn't want you using
scripts for this purpose, so we'll probably use the GUI and have
it generate a script for us to load on multiple servers and to
store in our documentation safe.
Regards,
Alan|||Its not really documented but you can get some guidance by click on help in
the job help dialog. Right click on your job and select help is a
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<ameyer2@.yahoo.com> wrote in message
news:1153261730.359715.126050@.i42g2000cwa.googlegroups.com...
> David Browne wrote:
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>|||Hilary Cotter wrote:
> Its not really documented but you can get some guidance by click on help i
n
> the job help dialog. Right click on your job and select help is a
> ...
Thanks Hilary.
I also just found this:
http://www.microsoft.com/technet/pr...s/c12ppcsq.mspx
It seems to give more information than is in the help file.
Alan|||ameyer2@.yahoo.com wrote:
> David Browne wrote:
>
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>
Hi Alan
Why don't you just create a DTS package and then run this package from
SQL server agent?
I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||Hello Steen. Thank you for the reply
Steen Persson (DK) wrote:
> Why don't you just create a DTS package and then run this package from
> SQL server agent?
Thanks for the suggestion. I will look into that.
> I must admit that I'm not quite sure what your problem is because I've
> used SQL agent for years for many different purposes and I haven't
> really seen that it add things I haven't asked for.
I presume you have mainly used the Agent GUI.
To see what I'm talking about, pick one of your Agent jobs
and export it as a text script, e.g.,
Open Agent.
Select any job
Right click on the job and select "All Tasks" / "Generate SQL
Script..."
Then examine what you get.
If you write your own script and submit it to SQL Server without
using the GUI front end, you can get your new job to show up in
the GUI list of jobs. However if you then use the GUI to generate
a script from it and compare what was generated to what you
input, you might be surprised. I was.
Alan|||ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>
> Thanks for the suggestion. I will look into that.
>
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Hi Alan
I still don't quite understand what your issue is. It's true that if I
generate a sql script from an existing job, there are more code in it,
but there's nothing I don't expect to be there. There are number of
checks if the job already exist etc. and that's all right for me. If you
don't check for this in your "manual" script you'll get an error if you
try to add a job that already exists so why shouldn't the check be there
when you generate the script?
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>
> Thanks for the suggestion. I will look into that.
>
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Perhaps you should analyze that additional code to determine what it's
doing? Maybe you're missing a step in your own scripts?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Perhaps you should analyze that additional code to determine what it's
> doing? Maybe you're missing a step in your own scripts?
>
I have indeed analyzed it. Some of what is there is stuff that either
I don't need because I've done the same thing another way, or
because I just don't need it.
Some is questionable. I'm not in front of SQL Server right now,
but as I recall, it wraps my entire job step in a transaction. That
may be right in the average case but wrong in particular cases
where it could defeat the intent of the programmer.
I can see why this approach by Microsoft has its fans. I'm
just not one of them.
But I didn't create this thread for the purpose of flaming
Microsoft. I recognize the MS has produced many fine
programs, SQL Server among them. I just wanted to know
if anyone knew of any documentation of the things MS does
under the covers of the Agent GUI.
I did find one source of information. See my first posting on
July 19 for the reference. If anyone knows of any other
documentation I'd love to see it.
Thanks.
Alan
Showing posts with label learn. Show all posts
Showing posts with label learn. Show all posts
Monday, March 12, 2012
Good SQL Server Agent book?
I plan to automate a process using about 20 steps and would
like to use SQL Server Agent. I'm finding it difficult to learn how
Agent works. The help files are skimpy and scattered and
leave many questions unanswered.
One thing I've noticed is that Agent does a lot of things behind
the curtain that the user did not request. If I write a script using
TSQL commands like sp_add_job, sp_add_job_step, etc., and
then invoke it via Agent, Agent does things that aren't in my
script. If I ask Agent to generate a script for my job it spits
out a script that includes most of what I ordered, but with
a lot of other boilerplate that I didn't order and some things
like transaction management, that may not have been what
I wanted.
Is all of this documented somewhere? Has someone written
a good book that covers this and gives recommendations on
the best ways to use Agent?
Thanks.
Alan<ameyer2@.yahoo.com> wrote in message
news:1153251901.175708.34630@.s13g2000cwa.googlegroups.com...
>I plan to automate a process using about 20 steps and would
> like to use SQL Server Agent. I'm finding it difficult to learn how
> Agent works. The help files are skimpy and scattered and
> leave many questions unanswered.
> One thing I've noticed is that Agent does a lot of things behind
> the curtain that the user did not request. If I write a script using
> TSQL commands like sp_add_job, sp_add_job_step, etc., and
> then invoke it via Agent, Agent does things that aren't in my
> script. If I ask Agent to generate a script for my job it spits
> out a script that includes most of what I ordered, but with
> a lot of other boilerplate that I didn't order and some things
> like transaction management, that may not have been what
> I wanted.
> Is all of this documented somewhere? Has someone written
> a good book that covers this and gives recommendations on
> the best ways to use Agent?
>
I would build your 20-step process in an SSIS package. Then deploy that
package as a 1-step SQL Agent job.
SSIS has a graphical workflow designer, integrated debugger, rich logging,
etc.
David|||David Browne wrote:
> ...
> I would build your 20-step process in an SSIS package. Then deploy that
> package as a 1-step SQL Agent job.
> SSIS has a graphical workflow designer, integrated debugger, rich logging,
> etc.
> David
Thanks David.
Unfortunately, we're still running SQLServer 2000, and it looks
like we'd have to upgrade our servers to SQL Server 2005 to
use SSIS. That may be more expensive and time consuming
than management would support just for this task.
Agent also has a graphical user interface, though I'm not sure
I wouldn't prefer submitting a script. The big advantage of a
script over a GUI, in my view, is that you can see everything
that happens in one listing, and if you're running multiple servers
you can easily move it to all of them. You can also document
a script with extensive comments.
However it looks like Microsoft really doesn't want you using
scripts for this purpose, so we'll probably use the GUI and have
it generate a script for us to load on multiple servers and to
store in our documentation safe.
Regards,
Alan|||Its not really documented but you can get some guidance by click on help in
the job help dialog. Right click on your job and select help is a
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<ameyer2@.yahoo.com> wrote in message
news:1153261730.359715.126050@.i42g2000cwa.googlegroups.com...
> David Browne wrote:
>> ...
>> I would build your 20-step process in an SSIS package. Then deploy that
>> package as a 1-step SQL Agent job.
>> SSIS has a graphical workflow designer, integrated debugger, rich
>> logging,
>> etc.
>> David
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>|||Hilary Cotter wrote:
> Its not really documented but you can get some guidance by click on help in
> the job help dialog. Right click on your job and select help is a
> ...
Thanks Hilary.
I also just found this:
http://www.microsoft.com/technet/prodtechnol/sql/2000/books/c12ppcsq.mspx
It seems to give more information than is in the help file.
Alan|||This is a multi-part message in MIME format.
--000609000409020907060701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> David Browne wrote:
>> ...
>> I would build your 20-step process in an SSIS package. Then deploy that
>> package as a 1-step SQL Agent job.
>> SSIS has a graphical workflow designer, integrated debugger, rich logging,
>> etc.
>> David
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>
Hi Alan
Why don't you just create a DTS package and then run this package from
SQL server agent?
I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--000609000409020907060701
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153261730.359715.126050@.i42g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">David Browne wrote:
</pre>
<blockquote type="cite">
<pre wrap="">...
I would build your 20-step process in an SSIS package. Then deploy that
package as a 1-step SQL Agent job.
SSIS has a graphical workflow designer, integrated debugger, rich logging,
etc.
David
</pre>
</blockquote>
<pre wrap=""><!-->
Thanks David.
Unfortunately, we're still running SQLServer 2000, and it looks
like we'd have to upgrade our servers to SQL Server 2005 to
use SSIS. That may be more expensive and time consuming
than management would support just for this task.
Agent also has a graphical user interface, though I'm not sure
I wouldn't prefer submitting a script. The big advantage of a
script over a GUI, in my view, is that you can see everything
that happens in one listing, and if you're running multiple servers
you can easily move it to all of them. You can also document
a script with extensive comments.
However it looks like Microsoft really doesn't want you using
scripts for this purpose, so we'll probably use the GUI and have
it generate a script for us to load on multiple servers and to
store in our documentation safe.
Regards,
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">Hi Alan<br>
<br>
Why don't you just create a DTS package and then run this package from
SQL server agent? <br>
I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--000609000409020907060701--|||Hello Steen. Thank you for the reply
Steen Persson (DK) wrote:
> Why don't you just create a DTS package and then run this package from
> SQL server agent?
Thanks for the suggestion. I will look into that.
> I must admit that I'm not quite sure what your problem is because I've
> used SQL agent for years for many different purposes and I haven't
> really seen that it add things I haven't asked for.
I presume you have mainly used the Agent GUI.
To see what I'm talking about, pick one of your Agent jobs
and export it as a text script, e.g.,
Open Agent.
Select any job
Right click on the job and select "All Tasks" / "Generate SQL
Script..."
Then examine what you get.
If you write your own script and submit it to SQL Server without
using the GUI front end, you can get your new job to show up in
the GUI list of jobs. However if you then use the GUI to generate
a script from it and compare what was generated to what you
input, you might be surprised. I was.
Alan|||This is a multi-part message in MIME format.
--090000090502030800020104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>
>> Why don't you just create a DTS package and then run this package from
>> SQL server agent?
> Thanks for the suggestion. I will look into that.
>
>> I must admit that I'm not quite sure what your problem is because I've
>> used SQL agent for years for many different purposes and I haven't
>> really seen that it add things I haven't asked for.
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Hi Alan
I still don't quite understand what your issue is. It's true that if I
generate a sql script from an existing job, there are more code in it,
but there's nothing I don't expect to be there. There are number of
checks if the job already exist etc. and that's all right for me. If you
don't check for this in your "manual" script you'll get an error if you
try to add a job that already exists so why shouldn't the check be there
when you generate the script?
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090000090502030800020104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153434437.302932.299920@.i42g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">Hello Steen. Thank you for the reply
Steen Persson (DK) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Why don't you just create a DTS package and then run this package from
SQL server agent?
</pre>
</blockquote>
<pre wrap=""><!-->
Thanks for the suggestion. I will look into that.
</pre>
<blockquote type="cite">
<pre wrap="">I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.
</pre>
</blockquote>
<pre wrap=""><!-->
I presume you have mainly used the Agent GUI.
To see what I'm talking about, pick one of your Agent jobs
and export it as a text script, e.g.,
Open Agent.
Select any job
Right click on the job and select "All Tasks" / "Generate SQL
Script..."
Then examine what you get.
If you write your own script and submit it to SQL Server without
using the GUI front end, you can get your new job to show up in
the GUI list of jobs. However if you then use the GUI to generate
a script from it and compare what was generated to what you
input, you might be surprised. I was.
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">Hi Alan<br>
<br>
I still don't quite understand what your issue is. It's true that if I
generate a sql script from an existing job, there are more code in it,
but there's nothing I don't expect to be there. There are number of
checks if the job already exist etc. and that's all right for me. If
you don't check for this in your "manual" script you'll get an error if
you try to add a job that already exists so why shouldn't the check be
there when you generate the script?<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090000090502030800020104--|||ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>> Why don't you just create a DTS package and then run this package from
>> SQL server agent?
> Thanks for the suggestion. I will look into that.
>> I must admit that I'm not quite sure what your problem is because I've
>> used SQL agent for years for many different purposes and I haven't
>> really seen that it add things I haven't asked for.
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Perhaps you should analyze that additional code to determine what it's
doing? Maybe you're missing a step in your own scripts?
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Perhaps you should analyze that additional code to determine what it's
> doing? Maybe you're missing a step in your own scripts?
>
I have indeed analyzed it. Some of what is there is stuff that either
I don't need because I've done the same thing another way, or
because I just don't need it.
Some is questionable. I'm not in front of SQL Server right now,
but as I recall, it wraps my entire job step in a transaction. That
may be right in the average case but wrong in particular cases
where it could defeat the intent of the programmer.
I can see why this approach by Microsoft has its fans. I'm
just not one of them.
But I didn't create this thread for the purpose of flaming
Microsoft. I recognize the MS has produced many fine
programs, SQL Server among them. I just wanted to know
if anyone knew of any documentation of the things MS does
under the covers of the Agent GUI.
I did find one source of information. See my first posting on
July 19 for the reference. If anyone knows of any other
documentation I'd love to see it.
Thanks.
Alan|||This is a multi-part message in MIME format.
--060304080400040803020408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> Tracy McKibben wrote:
>
>> Perhaps you should analyze that additional code to determine what it's
>> doing? Maybe you're missing a step in your own scripts?
>>
> I have indeed analyzed it. Some of what is there is stuff that either
> I don't need because I've done the same thing another way, or
> because I just don't need it.
> Some is questionable. I'm not in front of SQL Server right now,
> but as I recall, it wraps my entire job step in a transaction. That
> may be right in the average case but wrong in particular cases
> where it could defeat the intent of the programmer.
> I can see why this approach by Microsoft has its fans. I'm
> just not one of them.
> But I didn't create this thread for the purpose of flaming
> Microsoft. I recognize the MS has produced many fine
> programs, SQL Server among them. I just wanted to know
> if anyone knew of any documentation of the things MS does
> under the covers of the Agent GUI.
> I did find one source of information. See my first posting on
> July 19 for the reference. If anyone knows of any other
> documentation I'd love to see it.
> Thanks.
> Alan
>
You don't honestly expect that SQL server will produce a script that you
can just dump into some of you own code where you already has done a lot
of the checking that the script include?
When you right click on a job and script it out, SQL server can't do
anything else than produce a "stand-alone" script that can be run like
it is on it's own and then create the job you're asking for. For that
purpose I think it do the job very well and it include the code
necessary to do the job. This will (of course) also include a number of
checks and therefore also wrap it into a transaction that can be rolled
back in case of a failure.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--060304080400040803020408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153622611.152439.140660@.75g2000cwc.googlegroups.com"
type="cite">
<pre wrap="">Tracy McKibben wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Perhaps you should analyze that additional code to determine what it's
doing? Maybe you're missing a step in your own scripts?
</pre>
</blockquote>
<pre wrap=""><!-->I have indeed analyzed it. Some of what is there is stuff that either
I don't need because I've done the same thing another way, or
because I just don't need it.
Some is questionable. I'm not in front of SQL Server right now,
but as I recall, it wraps my entire job step in a transaction. That
may be right in the average case but wrong in particular cases
where it could defeat the intent of the programmer.
I can see why this approach by Microsoft has its fans. I'm
just not one of them.
But I didn't create this thread for the purpose of flaming
Microsoft. I recognize the MS has produced many fine
programs, SQL Server among them. I just wanted to know
if anyone knew of any documentation of the things MS does
under the covers of the Agent GUI.
I did find one source of information. See my first posting on
July 19 for the reference. If anyone knows of any other
documentation I'd love to see it.
Thanks.
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">You don't honestly expect that SQL
server will produce a script that you can just dump into some of you
own code where you already has done a lot of the checking that the
script include? <br>
When you right click on a job and script it out, SQL server can't do
anything else than produce a "stand-alone" script that can be run like
it is on it's own and then create the job you're asking for. For that
purpose I think it do the job very well and it include the code
necessary to do the job. This will (of course) also include a number of
checks and therefore also wrap it into a transaction that can be rolled
back in case of a failure.<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
<br>
</font></font>
</body>
</html>
--060304080400040803020408--|||Steen Persson (DK) wrote:
...
> You don't honestly expect that SQL server will produce a script that you
> can just dump into some of you own code where you already has done a lot
> of the checking that the script include?
...
Well, like I say, I'm not here to flame Microsoft or say that what
they've done doesn't meet most people's needs.
For myself, I would like to be able to submit a script to Agent and
have some assurance that what I submitted is exactly what gets
done. If the script has detectable errors, I'd like Agent to report
them to me rather than modify the script.
It may be that Agent does exactly what I tell it to do. Or it may be
that it reads my script, extracts things from it, adds whatever it
wants, and throws my original script away.
Even though I wouldn't like that behavior, it would be fine if
it were documented. My problem, the one that I posted
to start this thread, is that I couldn't find any documentation.
I don't even know whether the script Agent
generates is what it executes, or whether it executes my
script just as I submitted it and generates the script it
generates just for my benefit if I want to use it as the basis
for some other job.
I'm just looking for serious documentation - something beyond
"to do this - click that".
Alan
like to use SQL Server Agent. I'm finding it difficult to learn how
Agent works. The help files are skimpy and scattered and
leave many questions unanswered.
One thing I've noticed is that Agent does a lot of things behind
the curtain that the user did not request. If I write a script using
TSQL commands like sp_add_job, sp_add_job_step, etc., and
then invoke it via Agent, Agent does things that aren't in my
script. If I ask Agent to generate a script for my job it spits
out a script that includes most of what I ordered, but with
a lot of other boilerplate that I didn't order and some things
like transaction management, that may not have been what
I wanted.
Is all of this documented somewhere? Has someone written
a good book that covers this and gives recommendations on
the best ways to use Agent?
Thanks.
Alan<ameyer2@.yahoo.com> wrote in message
news:1153251901.175708.34630@.s13g2000cwa.googlegroups.com...
>I plan to automate a process using about 20 steps and would
> like to use SQL Server Agent. I'm finding it difficult to learn how
> Agent works. The help files are skimpy and scattered and
> leave many questions unanswered.
> One thing I've noticed is that Agent does a lot of things behind
> the curtain that the user did not request. If I write a script using
> TSQL commands like sp_add_job, sp_add_job_step, etc., and
> then invoke it via Agent, Agent does things that aren't in my
> script. If I ask Agent to generate a script for my job it spits
> out a script that includes most of what I ordered, but with
> a lot of other boilerplate that I didn't order and some things
> like transaction management, that may not have been what
> I wanted.
> Is all of this documented somewhere? Has someone written
> a good book that covers this and gives recommendations on
> the best ways to use Agent?
>
I would build your 20-step process in an SSIS package. Then deploy that
package as a 1-step SQL Agent job.
SSIS has a graphical workflow designer, integrated debugger, rich logging,
etc.
David|||David Browne wrote:
> ...
> I would build your 20-step process in an SSIS package. Then deploy that
> package as a 1-step SQL Agent job.
> SSIS has a graphical workflow designer, integrated debugger, rich logging,
> etc.
> David
Thanks David.
Unfortunately, we're still running SQLServer 2000, and it looks
like we'd have to upgrade our servers to SQL Server 2005 to
use SSIS. That may be more expensive and time consuming
than management would support just for this task.
Agent also has a graphical user interface, though I'm not sure
I wouldn't prefer submitting a script. The big advantage of a
script over a GUI, in my view, is that you can see everything
that happens in one listing, and if you're running multiple servers
you can easily move it to all of them. You can also document
a script with extensive comments.
However it looks like Microsoft really doesn't want you using
scripts for this purpose, so we'll probably use the GUI and have
it generate a script for us to load on multiple servers and to
store in our documentation safe.
Regards,
Alan|||Its not really documented but you can get some guidance by click on help in
the job help dialog. Right click on your job and select help is a
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<ameyer2@.yahoo.com> wrote in message
news:1153261730.359715.126050@.i42g2000cwa.googlegroups.com...
> David Browne wrote:
>> ...
>> I would build your 20-step process in an SSIS package. Then deploy that
>> package as a 1-step SQL Agent job.
>> SSIS has a graphical workflow designer, integrated debugger, rich
>> logging,
>> etc.
>> David
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>|||Hilary Cotter wrote:
> Its not really documented but you can get some guidance by click on help in
> the job help dialog. Right click on your job and select help is a
> ...
Thanks Hilary.
I also just found this:
http://www.microsoft.com/technet/prodtechnol/sql/2000/books/c12ppcsq.mspx
It seems to give more information than is in the help file.
Alan|||This is a multi-part message in MIME format.
--000609000409020907060701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> David Browne wrote:
>> ...
>> I would build your 20-step process in an SSIS package. Then deploy that
>> package as a 1-step SQL Agent job.
>> SSIS has a graphical workflow designer, integrated debugger, rich logging,
>> etc.
>> David
> Thanks David.
> Unfortunately, we're still running SQLServer 2000, and it looks
> like we'd have to upgrade our servers to SQL Server 2005 to
> use SSIS. That may be more expensive and time consuming
> than management would support just for this task.
> Agent also has a graphical user interface, though I'm not sure
> I wouldn't prefer submitting a script. The big advantage of a
> script over a GUI, in my view, is that you can see everything
> that happens in one listing, and if you're running multiple servers
> you can easily move it to all of them. You can also document
> a script with extensive comments.
> However it looks like Microsoft really doesn't want you using
> scripts for this purpose, so we'll probably use the GUI and have
> it generate a script for us to load on multiple servers and to
> store in our documentation safe.
> Regards,
> Alan
>
Hi Alan
Why don't you just create a DTS package and then run this package from
SQL server agent?
I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--000609000409020907060701
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153261730.359715.126050@.i42g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">David Browne wrote:
</pre>
<blockquote type="cite">
<pre wrap="">...
I would build your 20-step process in an SSIS package. Then deploy that
package as a 1-step SQL Agent job.
SSIS has a graphical workflow designer, integrated debugger, rich logging,
etc.
David
</pre>
</blockquote>
<pre wrap=""><!-->
Thanks David.
Unfortunately, we're still running SQLServer 2000, and it looks
like we'd have to upgrade our servers to SQL Server 2005 to
use SSIS. That may be more expensive and time consuming
than management would support just for this task.
Agent also has a graphical user interface, though I'm not sure
I wouldn't prefer submitting a script. The big advantage of a
script over a GUI, in my view, is that you can see everything
that happens in one listing, and if you're running multiple servers
you can easily move it to all of them. You can also document
a script with extensive comments.
However it looks like Microsoft really doesn't want you using
scripts for this purpose, so we'll probably use the GUI and have
it generate a script for us to load on multiple servers and to
store in our documentation safe.
Regards,
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">Hi Alan<br>
<br>
Why don't you just create a DTS package and then run this package from
SQL server agent? <br>
I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--000609000409020907060701--|||Hello Steen. Thank you for the reply
Steen Persson (DK) wrote:
> Why don't you just create a DTS package and then run this package from
> SQL server agent?
Thanks for the suggestion. I will look into that.
> I must admit that I'm not quite sure what your problem is because I've
> used SQL agent for years for many different purposes and I haven't
> really seen that it add things I haven't asked for.
I presume you have mainly used the Agent GUI.
To see what I'm talking about, pick one of your Agent jobs
and export it as a text script, e.g.,
Open Agent.
Select any job
Right click on the job and select "All Tasks" / "Generate SQL
Script..."
Then examine what you get.
If you write your own script and submit it to SQL Server without
using the GUI front end, you can get your new job to show up in
the GUI list of jobs. However if you then use the GUI to generate
a script from it and compare what was generated to what you
input, you might be surprised. I was.
Alan|||This is a multi-part message in MIME format.
--090000090502030800020104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>
>> Why don't you just create a DTS package and then run this package from
>> SQL server agent?
> Thanks for the suggestion. I will look into that.
>
>> I must admit that I'm not quite sure what your problem is because I've
>> used SQL agent for years for many different purposes and I haven't
>> really seen that it add things I haven't asked for.
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Hi Alan
I still don't quite understand what your issue is. It's true that if I
generate a sql script from an existing job, there are more code in it,
but there's nothing I don't expect to be there. There are number of
checks if the job already exist etc. and that's all right for me. If you
don't check for this in your "manual" script you'll get an error if you
try to add a job that already exists so why shouldn't the check be there
when you generate the script?
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090000090502030800020104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153434437.302932.299920@.i42g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">Hello Steen. Thank you for the reply
Steen Persson (DK) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Why don't you just create a DTS package and then run this package from
SQL server agent?
</pre>
</blockquote>
<pre wrap=""><!-->
Thanks for the suggestion. I will look into that.
</pre>
<blockquote type="cite">
<pre wrap="">I must admit that I'm not quite sure what your problem is because I've
used SQL agent for years for many different purposes and I haven't
really seen that it add things I haven't asked for.
</pre>
</blockquote>
<pre wrap=""><!-->
I presume you have mainly used the Agent GUI.
To see what I'm talking about, pick one of your Agent jobs
and export it as a text script, e.g.,
Open Agent.
Select any job
Right click on the job and select "All Tasks" / "Generate SQL
Script..."
Then examine what you get.
If you write your own script and submit it to SQL Server without
using the GUI front end, you can get your new job to show up in
the GUI list of jobs. However if you then use the GUI to generate
a script from it and compare what was generated to what you
input, you might be surprised. I was.
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">Hi Alan<br>
<br>
I still don't quite understand what your issue is. It's true that if I
generate a sql script from an existing job, there are more code in it,
but there's nothing I don't expect to be there. There are number of
checks if the job already exist etc. and that's all right for me. If
you don't check for this in your "manual" script you'll get an error if
you try to add a job that already exists so why shouldn't the check be
there when you generate the script?<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090000090502030800020104--|||ameyer2@.yahoo.com wrote:
> Hello Steen. Thank you for the reply
> Steen Persson (DK) wrote:
>> Why don't you just create a DTS package and then run this package from
>> SQL server agent?
> Thanks for the suggestion. I will look into that.
>> I must admit that I'm not quite sure what your problem is because I've
>> used SQL agent for years for many different purposes and I haven't
>> really seen that it add things I haven't asked for.
> I presume you have mainly used the Agent GUI.
> To see what I'm talking about, pick one of your Agent jobs
> and export it as a text script, e.g.,
> Open Agent.
> Select any job
> Right click on the job and select "All Tasks" / "Generate SQL
> Script..."
> Then examine what you get.
> If you write your own script and submit it to SQL Server without
> using the GUI front end, you can get your new job to show up in
> the GUI list of jobs. However if you then use the GUI to generate
> a script from it and compare what was generated to what you
> input, you might be surprised. I was.
> Alan
>
Perhaps you should analyze that additional code to determine what it's
doing? Maybe you're missing a step in your own scripts?
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Perhaps you should analyze that additional code to determine what it's
> doing? Maybe you're missing a step in your own scripts?
>
I have indeed analyzed it. Some of what is there is stuff that either
I don't need because I've done the same thing another way, or
because I just don't need it.
Some is questionable. I'm not in front of SQL Server right now,
but as I recall, it wraps my entire job step in a transaction. That
may be right in the average case but wrong in particular cases
where it could defeat the intent of the programmer.
I can see why this approach by Microsoft has its fans. I'm
just not one of them.
But I didn't create this thread for the purpose of flaming
Microsoft. I recognize the MS has produced many fine
programs, SQL Server among them. I just wanted to know
if anyone knew of any documentation of the things MS does
under the covers of the Agent GUI.
I did find one source of information. See my first posting on
July 19 for the reference. If anyone knows of any other
documentation I'd love to see it.
Thanks.
Alan|||This is a multi-part message in MIME format.
--060304080400040803020408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
ameyer2@.yahoo.com wrote:
> Tracy McKibben wrote:
>
>> Perhaps you should analyze that additional code to determine what it's
>> doing? Maybe you're missing a step in your own scripts?
>>
> I have indeed analyzed it. Some of what is there is stuff that either
> I don't need because I've done the same thing another way, or
> because I just don't need it.
> Some is questionable. I'm not in front of SQL Server right now,
> but as I recall, it wraps my entire job step in a transaction. That
> may be right in the average case but wrong in particular cases
> where it could defeat the intent of the programmer.
> I can see why this approach by Microsoft has its fans. I'm
> just not one of them.
> But I didn't create this thread for the purpose of flaming
> Microsoft. I recognize the MS has produced many fine
> programs, SQL Server among them. I just wanted to know
> if anyone knew of any documentation of the things MS does
> under the covers of the Agent GUI.
> I did find one source of information. See my first posting on
> July 19 for the reference. If anyone knows of any other
> documentation I'd love to see it.
> Thanks.
> Alan
>
You don't honestly expect that SQL server will produce a script that you
can just dump into some of you own code where you already has done a lot
of the checking that the script include?
When you right click on a job and script it out, SQL server can't do
anything else than produce a "stand-alone" script that can be run like
it is on it's own and then create the job you're asking for. For that
purpose I think it do the job very well and it include the code
necessary to do the job. This will (of course) also include a number of
checks and therefore also wrap it into a transaction that can be rolled
back in case of a failure.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--060304080400040803020408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:ameyer2@.yahoo.com">ameyer2@.yahoo.com</a> wrote:
<blockquote
cite="mid1153622611.152439.140660@.75g2000cwc.googlegroups.com"
type="cite">
<pre wrap="">Tracy McKibben wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Perhaps you should analyze that additional code to determine what it's
doing? Maybe you're missing a step in your own scripts?
</pre>
</blockquote>
<pre wrap=""><!-->I have indeed analyzed it. Some of what is there is stuff that either
I don't need because I've done the same thing another way, or
because I just don't need it.
Some is questionable. I'm not in front of SQL Server right now,
but as I recall, it wraps my entire job step in a transaction. That
may be right in the average case but wrong in particular cases
where it could defeat the intent of the programmer.
I can see why this approach by Microsoft has its fans. I'm
just not one of them.
But I didn't create this thread for the purpose of flaming
Microsoft. I recognize the MS has produced many fine
programs, SQL Server among them. I just wanted to know
if anyone knew of any documentation of the things MS does
under the covers of the Agent GUI.
I did find one source of information. See my first posting on
July 19 for the reference. If anyone knows of any other
documentation I'd love to see it.
Thanks.
Alan
</pre>
</blockquote>
<font size="-1"><font face="Arial">You don't honestly expect that SQL
server will produce a script that you can just dump into some of you
own code where you already has done a lot of the checking that the
script include? <br>
When you right click on a job and script it out, SQL server can't do
anything else than produce a "stand-alone" script that can be run like
it is on it's own and then create the job you're asking for. For that
purpose I think it do the job very well and it include the code
necessary to do the job. This will (of course) also include a number of
checks and therefore also wrap it into a transaction that can be rolled
back in case of a failure.<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
<br>
</font></font>
</body>
</html>
--060304080400040803020408--|||Steen Persson (DK) wrote:
...
> You don't honestly expect that SQL server will produce a script that you
> can just dump into some of you own code where you already has done a lot
> of the checking that the script include?
...
Well, like I say, I'm not here to flame Microsoft or say that what
they've done doesn't meet most people's needs.
For myself, I would like to be able to submit a script to Agent and
have some assurance that what I submitted is exactly what gets
done. If the script has detectable errors, I'd like Agent to report
them to me rather than modify the script.
It may be that Agent does exactly what I tell it to do. Or it may be
that it reads my script, extracts things from it, adds whatever it
wants, and throws my original script away.
Even though I wouldn't like that behavior, it would be fine if
it were documented. My problem, the one that I posted
to start this thread, is that I couldn't find any documentation.
I don't even know whether the script Agent
generates is what it executes, or whether it executes my
script just as I submitted it and generates the script it
generates just for my benefit if I want to use it as the basis
for some other job.
I'm just looking for serious documentation - something beyond
"to do this - click that".
Alan
good SQL book?
hello, for a new job i might have to learn SQL. i've never
worked with databases or SQL, so i'll need to learn. can
anybody advice me on what would be a good book to learn
from? i'm quite an experienced programmer, so it doesn't
have to be a dummies guide, and preferably not a bulky book
like the "SQL bible" or something.
worked with databases or SQL, so i'll need to learn. can
anybody advice me on what would be a good book to learn
from? i'm quite an experienced programmer, so it doesn't
have to be a dummies guide, and preferably not a bulky book
like the "SQL bible" or something.
oh, one of my 'favourite' computer books of all times is
"thinking in Java" by bruce eckel, to give you an idea.
mike
--
not sure if there's a better group to ask these questionsmichael nieuwenhuizen wrote:
> hello, for a new job i might have to learn SQL. i've never
> worked with databases or SQL, so i'll need to learn. can
> anybody advice me on what would be a good book to learn
> from? i'm quite an experienced programmer, so it doesn't
> have to be a dummies guide, and preferably not a bulky book
> like the "SQL bible" or something.
> oh, one of my 'favourite' computer books of all times is
> "thinking in Java" by bruce eckel, to give you an idea.
> mike
> --
> not sure if there's a better group to ask these questions
Probably the best of breed is Joe Celko's "SQL For Smarties" but I
wouldn't call it a beginner's book by any stretch of the imagination.
Put it on your list for book number 2 or 3.
Also, remember that TransactSQL is no more generic than is Oracle's
PL/SQL or any other vendor's implementation. So make sure the SQL book
you get is one that is oriented toward the RDBMS on which you will be
working.
--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)|||"Daniel Morgan" <damorgan@.x.washington.edu> wrote
> Probably the best of breed is Joe Celko's "SQL For Smarties" but I
> wouldn't call it a beginner's book by any stretch of the imagination.
i actually browsed through that one and it looked pretty impressive ...
and then i saw it wasn;t for the beginner ...
> Put it on your list for book number 2 or 3.
will do. thanks.
> Also, remember that TransactSQL is no more generic than is Oracle's
> PL/SQL or any other vendor's implementation.
i really don't have a clue about SQL. aren't all the SQL's based on
one version?
> So make sure the SQL book you get is one that is oriented toward the
> RDBMS on which you will be working.
it would probably be Oracle.
mike
--
and i have no experience with that either|||michael nieuwenhuizen wrote:
> i really don't have a clue about SQL. aren't all the SQL's based on
> one version?
SQL is an ANSI standard language. But the ANSI standard is not one thing
... it is at least three. And within that standard every vendor has lots
of room to implement that standard by any means they wish. Then they all
add proprietary language extensions to differentiate their product from
the others (more cynical minds would say to lock in their customers).
>>So make sure the SQL book you get is one that is oriented toward the
>>RDBMS on which you will be working.
>
> it would probably be Oracle.
> mike
Then I'd suggest reposting your question in an Oracle usenet group (such
as comp.databases.oracle.server) so that we don't offend our hosts by
being off-topic. But you can find all of the Oracle SQL you could
possibly hope to find at http://tahiti.oracle.com.
--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)|||The Guru's Guide to Transact-SQL by Ken Henderson
http://www.amazon.com/exec/obidos/t...536720?v=glance
Good SQL Book
hello
i am just starting to learn sql and know the basics, but now im looking for a good book to learn some more. A book that covers stored procedure would be very useful. If possible a book with q and a would be very good because i feel this tests if u understand what was just explaned. but if there is a good book without this it is ok. All sugestions welcome
NubNub
I'd just go on amazon and search for "T-SQL". Most books will be the same because the underlying concepts are all very similar. Personally I go to the W3's tutorial websites for everything but then again I am too cheap for books.
Good sp patterns
I am looking for a good document or whatever to learn how to create
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanks
If you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 Programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>
|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 Programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
>
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanks
If you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 Programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>
|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 Programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
>
Good sp patterns
I am looking for a good document or whatever to learn how to create
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanksIf you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 Programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 Programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> > I am looking for a good document or whatever to learn how to create
> > storedprocedure(select,Insert,...) effectively?
> >
> > I am going to create some storeprocedure and I want them to be nice in
> > performance and scalability.
> >
> > thanks
> >
> >
>
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanksIf you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 Programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 Programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> > I am looking for a good document or whatever to learn how to create
> > storedprocedure(select,Insert,...) effectively?
> >
> > I am going to create some storeprocedure and I want them to be nice in
> > performance and scalability.
> >
> > thanks
> >
> >
>
Good sp patterns
I am looking for a good document or whatever to learn how to create
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanksIf you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
>
storedprocedure(select,Insert,...) effectively?
I am going to create some storeprocedure and I want them to be nice in
performance and scalability.
thanksIf you are asking about a nicely-formatted template or some general dos and
donts, I am sure there are folks out here who have something to offer. But
to have a guide line for writing good performing and easy scaling procs, it
can cost a book and a few years of experience ...
Besides, it is always dependent on YOUR system. In addition, the
performance and scalability of stored procedures are not just in themselves.
It starts with logical DB design, physical implementation, etc.
Some books may be helpful. SQL Server 2000 Performance Tuning by Ed Whalen
et al, Professional SQL Server 2000 programming by R. Vieira can be among
them.
"ALI-R" <ali@.microsoft.com> wrote in message
news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> I am looking for a good document or whatever to learn how to create
> storedprocedure(select,Insert,...) effectively?
> I am going to create some storeprocedure and I want them to be nice in
> performance and scalability.
> thanks
>|||Is there somehwhere like www.codeprojects.com ,where I can find some
storedprocedure samples to get some idea how to write my stored procedures.
thanks for your help.
Ali
"Quentin Ran" <removethis.qran2@.yahoo.com> wrote in message
news:ujmD$lSwEHA.2316@.TK2MSFTNGP15.phx.gbl...
> If you are asking about a nicely-formatted template or some general dos
and
> donts, I am sure there are folks out here who have something to offer.
But
> to have a guide line for writing good performing and easy scaling procs,
it
> can cost a book and a few years of experience ...
> Besides, it is always dependent on YOUR system. In addition, the
> performance and scalability of stored procedures are not just in
themselves.
> It starts with logical DB design, physical implementation, etc.
> Some books may be helpful. SQL Server 2000 Performance Tuning by Ed
Whalen
> et al, Professional SQL Server 2000 programming by R. Vieira can be among
> them.
>
> "ALI-R" <ali@.microsoft.com> wrote in message
> news:%2328NHORwEHA.3416@.TK2MSFTNGP09.phx.gbl...
>
Wednesday, March 7, 2012
Good book for learning the Stored Proc language
Though I have been using SQL Server for some years, it is just recently that I have need to learn how to write SP's. I would like a recommendation for a book that is rich with examples (my best learning style).
Many thanks...
Todd
I highly recommend two Microsoft Press books with Itzak Ben-Gan as the primary author.
Inside T-SQL Programming
Inside T-SQL Querying
Also with Microsoft Press, Burst/Forte's title: Programming SQL Server 2005
Subscribe to:
Posts (Atom)