I'm creating many queries and stored procedures and would like to save them to the database instead of a file or cut and paste, etc.

Am I missing something or is there no way to save a query to anything other than a file in the Query Analyzer tool?

Thanks!d

Greetings -

If you are creating many queries, chances are you're probably going to run them over and over again. So, you may want to consider creating stored procedures. That would be the equivalent of "saving" the queries - as you are asking. In addition, stored procedures offer a lot of flexibility beyond the static query you'd save as a text file - query.sql which you'd load and run time and again.. Check out www.sqlteam.com (this is one of many sites out there) which can help you out with stored procedures, as well as the wrox books. I found SQL Server 2000 Programming a great book...

But, if all you need to do is save the query to the database and run it whenever you want - try this:

1) Incorporate your query as outlined below into a CREATE stored procedure syntax:

Your query:
SELECT <COLUMNS> FROM <TABLENAME> WHERE <CONDITION>

Create Stored Procedure syntax:
CREATE PROCEDURE uspMyStoredProdedure
AS
SELECT <COLUMNS> FROM <TABLENAME> WHERE <CONDITION>
GO

2) Then you can EXECUTE that stored procedure as often as you'd like to:

In query analzyer: EXECUTE MyStoredProcedure


That should get you started....

Ad hoc queries cannot be saved to the database. (Where would they go?)

Views and stored procedures can be saved by using the CREATE VIEW and CREATE PROCEDURE commands (part of the view or procedure itself). See BOL.

Jeff Mason
Custom Apps, Inc.
www.custom-apps.com

I think I see what you mean. I've been starting all my views and procedures with:
   ALTER VIEW..... or CREATE PROCEDURE

By doing this, will the view or procedure be created, altered, etc. each time I run it in the Query Analyzer?

Thanks,
Joe

Yup. The CREATE/ALTER VIEW/PROCEDURE, is a statement, which when executed by SQL Server, however it is executed (Query Analyzer, EM, via ADO, etc), will create/alter a view/procedure.

Don't include these statements unless you mean to change the object in the database.

Jeff Mason
Custom Apps, Inc.
www.custom-apps.com