[dba-SQLServer] Viewing and Modifying stored procedures

Robert,

It is interesting that you thought I was complaining, because in my mind
that is not what was happening.  I was asking for help, trying to grasp
a concept, thinking that I am not explaining myself well, so I try to
restate my question to be more clear.  When, yes, it is me who is not
understanding.  Now I think I do, thanks to everyone's help.

Jennifer

-----Original Message-----
From: Robert [mailto:rl_stewart at highstream.net] 
Sent: Wednesday, June 27, 2007 1:40 PM
To: dba-sqlserver at databaseadvisors.com
Cc: jengross at gte.net
Subject: Re: Viewing and Modifying stored procedures


Jennifer,

It was not meant as animosity.  I am trying to lay
out the facts of it to you. Yet, you keep trying
to find a way to do it the way you want it to
work.  It simply does not do it. I learned a
long time ago to not beat my head against the
Microsoft Brick Wall. It is the way they do it.
I prefer not to get a bloody forehead and headaches.
So, I walk around the barriers they throw up and
use it without complaining. It simply is a waste of
time and effort to complain.  There is too much to
do to keep up as it is without wasting the time and
effort on things that I cannot change. And, yes
it was direct criticism. I am trying to save you
from banging your head against that wall. Concentrate
your efforts on learning, not complaining. You will
get much further and have much better code and
programs in general if you will do that.

I apologize for the perception you got that my words
carried animosity toward you.  Again, none was intended.

I read through the other answers to your last post and
I think that you have it.  Except for one minor thing.
When you save an SP, it will bring up a dialog box asking
you where you want to save it to.  It then will save it as
a script that can then be put into a version control system
or used at a later date to synchronize changes made in a development
system to a production system.  Because of this, moving changes, it will
also be very good if you learn the DDL (data definition language)
portion of T-SQL so you can also script changes to the tables, indexes,
constraints and such.

The only way a change is made to the SP once it is created
is through the ALTER PROCEDURE portion of the statement. Similarly,you
can only create one using the CREATE PROCEDURE portion of the statement.
Once you get accustomed to it, it really does make sense.

Access shields us from a lot of things.  It is actually more difficult,
I think, to create an SP in an Access ADP program than in Management
Studio. And, there are limits to how Access can handle SPs as well.  It
does not like the use of temporary tables at all.

Robert

At 03:25 PM 6/27/2007, you wrote:
>Date: Wed, 27 Jun 2007 11:54:04 -0700
>From: "Jennifer Gross" <jengross at gte.net>
>Subject: Re: [dba-SQLServer] Viewing and Modifying stored procedures
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <010301c7b8ec$8bcf9be0$6501a8c0 at jefferson>
>Content-Type: text/plain; charset=us-ascii
>
>Hi Robert,
>
>Wow.  I never expected or received such animosity and direct criticism 
>from a request for help from this list or any other I belong to.
>
>Jennifer