Print in Trigger Statements.....

SQL Server books online has 'print' statements in the trigger examples.
Where exactly the print will happen? How to get benefit of this while
debugging?
Thanks,
Jessy
You can make execution visible in the query analyzer, can print out some
information about filled variables, rowcounts, status of transactions etc.
While debugging you can also watch the value of the variable with the
properties pane.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Jessy Martin" <Jessy_Smith79@.hotmail.com> schrieb im Newsbeitrag
news:%23MweP25ZFHA.616@.TK2MSFTNGP12.phx.gbl...
> SQL Server books online has 'print' statements in the trigger examples.
> Where exactly the print will happen? How to get benefit of this while
> debugging?
> Thanks,
> Jessy
>

Print in Trigger Statements.....

SQL Server books online has 'print' statements in the trigger examples.
Where exactly the print will happen? How to get benefit of this while
debugging?
Thanks,
JessyYou can make execution visible in the query analyzer, can print out some
information about filled variables, rowcounts, status of transactions etc.
While debugging you can also watch the value of the variable with the
properties pane.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Jessy Martin" <Jessy_Smith79@.hotmail.com> schrieb im Newsbeitrag
news:%23MweP25ZFHA.616@.TK2MSFTNGP12.phx.gbl...
> SQL Server books online has 'print' statements in the trigger examples.
> Where exactly the print will happen? How to get benefit of this while
> debugging?
> Thanks,
> Jessy
>sql

Print in Trigger Statements.....

SQL Server books online has 'print' statements in the trigger examples.
Where exactly the print will happen? How to get benefit of this while
debugging?
Thanks,
JessyYou can make execution visible in the query analyzer, can print out some
information about filled variables, rowcounts, status of transactions etc.
While debugging you can also watch the value of the variable with the
properties pane.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Jessy Martin" <Jessy_Smith79@.hotmail.com> schrieb im Newsbeitrag
news:%23MweP25ZFHA.616@.TK2MSFTNGP12.phx.gbl...
> SQL Server books online has 'print' statements in the trigger examples.
> Where exactly the print will happen? How to get benefit of this while
> debugging?
> Thanks,
> Jessy
>

Print Books on-line

Is it possible to print booksonline? If so do i need a separate download or is there a trick to print them like a book?

Thanks

Um...............to do what?

The last time I saw a printed version of BOL was back in SQL Server 6.5 and that thing was a shelf containing a couple thousand pages. Someone on the doc team would know how many pages there actually are now. But, I would expect BOL for just the replication engine to weigh in at somewhere north of 700 pages. The whole thing? You would need a semi full of paper, a couple hundred toner cartridges, and about a dozen very high speed printers running non-stop for weeks to print all of this stuff out. There has to be somewhere in excess of 50,000 pages based on the fact that BOL is 100MB of highly compressed documents most of which is text.

|||

Bloody ell!!!!! i thought it was about 600 pages so i can have it printed for offline reading when im not at the office - guess thats out the window.

Thanks anyway

|||

Yeah, I hear you. But what about just printing, say, the T-Sql reference manual. I like to have hard copy sometimes (back patio, couch, etc), sometimes the printed page is just more convenient. Anyway, does anyone know a way to print one manual from the BOL? That is, without having to go to each link and print separately, something like the online Oracle docs do it - view this on-line, or print pdf here.

Kevin

|||No, there isn't. Books Online went...Online years ago for the simple reason that publishing it in any other form than electronic was prohibitive. The last time I saw a printed version was with 6.5 and that came in multiple volumes at somewhere around 3000 total pages. 3000 pages wouldn't even cover most of the manuals in the collection. You might be able to get the full text manual is a small enough set of pages to print out, but there still isn't a way to print anything other than printing something one page at a time. BOL is too big and is not written for printing. The entire authoriing process is built on an individual topic basis, designed to be hyperlinked to other topics, and built for online viewing and searching only. It's not meant to be read from point A to point B like a book, but instead to be read in a non-linear manner after looking up a specifc topic.

Print Books on-line

Is it possible to print booksonline? If so do i need a separate download or is there a trick to print them like a book?

Thanks

Um...............to do what?

The last time I saw a printed version of BOL was back in SQL Server 6.5 and that thing was a shelf containing a couple thousand pages. Someone on the doc team would know how many pages there actually are now. But, I would expect BOL for just the replication engine to weigh in at somewhere north of 700 pages. The whole thing? You would need a semi full of paper, a couple hundred toner cartridges, and about a dozen very high speed printers running non-stop for weeks to print all of this stuff out. There has to be somewhere in excess of 50,000 pages based on the fact that BOL is 100MB of highly compressed documents most of which is text.

|||

Bloody ell!!!!! i thought it was about 600 pages so i can have it printed for offline reading when im not at the office - guess thats out the window.

Thanks anyway

|||

Yeah, I hear you. But what about just printing, say, the T-Sql reference manual. I like to have hard copy sometimes (back patio, couch, etc), sometimes the printed page is just more convenient. Anyway, does anyone know a way to print one manual from the BOL? That is, without having to go to each link and print separately, something like the online Oracle docs do it - view this on-line, or print pdf here.

Kevin

|||No, there isn't. Books Online went...Online years ago for the simple reason that publishing it in any other form than electronic was prohibitive. The last time I saw a printed version was with 6.5 and that came in multiple volumes at somewhere around 3000 total pages. 3000 pages wouldn't even cover most of the manuals in the collection. You might be able to get the full text manual is a small enough set of pages to print out, but there still isn't a way to print anything other than printing something one page at a time. BOL is too big and is not written for printing. The entire authoriing process is built on an individual topic basis, designed to be hyperlinked to other topics, and built for online viewing and searching only. It's not meant to be read from point A to point B like a book, but instead to be read in a non-linear manner after looking up a specifc topic.

Primary Key: I am trying to understand--please help if you can.

Hi all,

So I've been reading the newsgroups, and reading a few books trying to learn
SQL and SQL Server 2000. The books tell me I need a Primary Key, and that
every table should have one. I know (I think) that a Primary Key is a
special field that uniquely identifies each record or row within a table.

My question is this: If I have a field or column whose values are all (and
will be) different in every row, is that what a Primary Key is, or is it not
a primary key until I designate it as such with either a statement or by
right-clicking a little key on the table diagram.

If so, then what is the reason _behind_ why I have to do that, and have a
primary key?

I've been playing with a few tables, and I can select information just fine,
relate tables together with joins, and everything works fine (so far) all
without my designating any Primary Keys--so why, exactly, do I need one, and
exactly what is it?

I would appreciate any help and clarification.

Thanks.Replied in microsoft.public.sqlserver.programming.

Please don't multi-post.

--
David Portas
SQL Server MVP
--|||David Portas scratched out in the sand

> Replied in microsoft.public.sqlserver.programming.
> Please don't multi-post.

...and for those of us who don't subscribe to m.p.s.p, your answer, David,
was...?

--
kai - kai at 3gproductions dot com
www.gamephreakz.com || www.filesite.org
"friends don't let friends use windows xp"|||Hi Mavis,

As you suggest, a Primary key is a constraint on the column requiring that
every value is (and will be) different
in every row. Furthermore, it requires that no row can have a NULL value for
that column. So those are the restrictions
on a Primary Key field, that it be non-null and that each value be unique.
Further, a Primary Key can be made up of more than
one column. So, each table can have only one Primary Key, but it can be
made up of several columns. (jeesh- so far I'm probably
just making this MORE confusing).

So, although those are the characteristics of a Primary Key, a column is not
one until you designate it as such. The reason behind it is
twofold (there may be more reasons, but only two come to mind at the
moment - Note to self: more coffee):
1. Performance - when you designate a column as a Primary Key, it is
(clustered) indexed to assist in data retrieval.
2. Data Integrity - the database will ensure that every value that is
inserted (or updated) in the table will meet the requirements of a
Primary Key (i.e. unique and non-null) so you don't have to write those
checks into application code.

It's assumed that the Primary Key field will typically be the field used in
table joins, so because it's indexed (it's also a good general plan
to index the foreign key field) your queries will perform better.

I hope this is of some help Mavis,

Steve

"Mavis Tilden" <mavistilden@.hotmail.com> wrote in message
news:XVead.9397$3C6.206028@.news20.bellglobal.com.. .
> Hi all,
> So I've been reading the newsgroups, and reading a few books trying to
learn
> SQL and SQL Server 2000. The books tell me I need a Primary Key, and that
> every table should have one. I know (I think) that a Primary Key is a
> special field that uniquely identifies each record or row within a table.
> My question is this: If I have a field or column whose values are all (and
> will be) different in every row, is that what a Primary Key is, or is it
not
> a primary key until I designate it as such with either a statement or by
> right-clicking a little key on the table diagram.
> If so, then what is the reason _behind_ why I have to do that, and have a
> primary key?
> I've been playing with a few tables, and I can select information just
fine,
> relate tables together with joins, and everything works fine (so far) all
> without my designating any Primary Keys--so why, exactly, do I need one,
and
> exactly what is it?
> I would appreciate any help and clarification.
> Thanks.|||On Mon, 11 Oct 2004 04:50:11 -0700, filesiteguy wrote:

>David Portas scratched out in the sand
>> Replied in microsoft.public.sqlserver.programming.
>>
>> Please don't multi-post.
>>
>...and for those of us who don't subscribe to m.p.s.p, your answer, David,
>was...?

Hi filesiteguy,

http://www.google.com/groups?hl=en&...bellglobal.com

Best, Hugo
--

(Remove _NO_ and _SPAM_ to get my e-mail address)

Previous Function - Help

Newbie question. I have searched the posts and have found a few that say the
previous function works. The documentation in the online books is a little
sketchy. Does someone have a detailed example? If not, could someone point
me to more detailed documentation on this function?
Thanks,
RickThe documentation about the Previous() function is actually incorrect
because it describes multiple parameters. The Previous function only has one
argument which is an expression and you can use Previous() only in a list or
a table.
Example:
=Previous(Fields!A.Value)
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:A47E8613-9078-4610-A528-FC5923197318@.microsoft.com...
> Newbie question. I have searched the posts and have found a few that say
> the
> previous function works. The documentation in the online books is a
> little
> sketchy. Does someone have a detailed example? If not, could someone
> point
> me to more detailed documentation on this function?
> Thanks,
> Rick|||Thanks Robert. Works like a champ.
"Robert Bruckner [MSFT]" wrote:
> The documentation about the Previous() function is actually incorrect
> because it describes multiple parameters. The Previous function only has one
> argument which is an expression and you can use Previous() only in a list or
> a table.
> Example:
> =Previous(Fields!A.Value)
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Rick" <Rick@.discussions.microsoft.com> wrote in message
> news:A47E8613-9078-4610-A528-FC5923197318@.microsoft.com...
> > Newbie question. I have searched the posts and have found a few that say
> > the
> > previous function works. The documentation in the online books is a
> > little
> > sketchy. Does someone have a detailed example? If not, could someone
> > point
> > me to more detailed documentation on this function?
> >
> > Thanks,
> > Rick
>
>