sql server (alternate): hi.
coming from postgresql, i am used to textual references to most of the
things i do with the database. i feel a little lost with all the graphical.

i have few questions regarding MS SQL 2000
1. what is the best (or easiest) way of getting a table definition in text?
it could be either a CREATE TABLE sql-query or a just a definition,
something like:
TABLE thisTable
id integer
value varchar(10)
etc. etc.


2a. how do i get a query plan and how do i get it in text.
2b. are there planner modes that show more or less of what actually
happened, verbose mode perhaps?
2c. if i ask for a query plan, will SQL server actually run the query or
will it only produce a plan. if the query is run, does it commit or
rollback by default?

Hi

I assume you have found books online that will give you a great deal of
information regarding language/tools etc... the latest version can be
downloaded from
http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en

This will give you information on sp_help (and similar procedures) which
will give information regarding an object.

Scripting can be done from Enterprise Manager, the General SQL option will
create a script to create the object which can be written to a file or
pasted into another window. This can usually be found by right clicking the
item in the tree view.

There are also scripting options in Query Analyser if you display the object
browser. This gives you multiple options regarding how you want to script it
and where output should go. This is also usually a right click option.

John


You can look at sp_help
[quoted text, click to view]

stig (_nospam_stigerikson@yahoo.se) writes:
[quoted text, click to view]

Here are some good news: you don't have to use it. Use Query Analyzer
for all your tasks, and leave Enterprise Manager to rot in a corner.

Personally, I do almost all tasks from Query Analyzer, and about the only
graphical thing there is the query plan. The only thing I do from
Enterprise Manager is to deal with jobs.




--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at

Hugo Kornelis (hugo@pe_NO_rFact.in_SPAM_fo) writes:
[quoted text, click to view]

No, SET SHOWPLAN_TEXT (and SHOWPLAN_ALL) ON turns off execution:

SET SHOWPLAN_TEXT ON
go
PRINT 'Showplan is ON'
go
SET SHOWPLAN_TEXT OFF
go
PRINT 'Showplan is OFF'
go

The command to use if you want plans and also execute, is
SET STATISTICS PROFILE ON.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at

[quoted text, click to view]

Hi Stig,

Answers inline.


[quoted text, click to view]

John Bell already addressed this question.


[quoted text, click to view]

To get an execution plan in text, add
SET SHOWPLAN_TEXT ON
go
before your query.
When using Query Analyzer, you can also use either Query | Current
connection properties (for one connection) or Tools | Options |
Connection properties (to change the defaults) and add a tick before the
"Set showplan_text" option.

[quoted text, click to view]

I personally prefer the graphical version offered by Query Analyzer over
the text version offered by SET SHOWPLAN_TEXT ON, but both carry
essentially the same information.

[quoted text, click to view]

In QA, you can use Query | Display Estimated Execution Plan (Ctrl-L) to
get an estimate of the query plan without running the query, or you can
get the real execution plan, including statistics on actually processed
numbers of rows, by running the query with the option Query | Show
Execution Plan (Ctrl-K) turned on - this will actually run the query.

If you use the SET SHOWPLAN_TEXT ON option, the query will actualy be
run, unless you also activate the fmtonly option with the commands
SET FMTONLY ON
go


Best, Hugo
--

[quoted text, click to view]

(snip)
[quoted text, click to view]

Hi Stig,

Sorry - clicked "Send" before answering the last question.

If the query is run, it will commit by default, unless:

a) you explicitly execute a BEGIN TRANSACTION command before it (in that
case, the transaction remains open until you explicitly ROLLBACK or
COMMIT it or until the connection is lost),

b) you have activated the inplicit_transactions option, in which case
SQL Server will act as there is a BEGIN TRANSACTION command even if you
didn't add it yourself, or

c) it aborts due to an error (in that case, it gets rolled back).

Best, Hugo
--

[quoted text, click to view]

Hi Erland,

You're right. Thanks for putting me straight.

I guess it's time to write another 1000 lines of "never post without
testing" :-(

Best, Hugo
--

[quoted text, click to view]

No, you just have to create a query that does so.

Please post DDL and all statements. :-)


[quoted text, click to view]