Transaction

Question

Post reply

Transaction

Pulivarthi Sasidhar

SSCertifiable

Points: 6706
More actions
October 12, 2013 at 11:57 am

#299640

Comments posted to this topic are about the item Transaction

Viewing 15 posts - 1 through 15 (of 47 total)

You must be logged in to reply to this topic. Login to reply

Ron McCullough SSC Guru Points: 63877 More actions · Answer 1

Too simple .....

If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read[/url]
Before posting a performance problem please read[/url]

Carlo Romagnano SSC-Insane Points: 22667 More actions · Answer 2

Carlo Romagnano

SSC-Insane

Points: 22667

October 13, 2013 at 10:34 am

#1658133

Clear and easy question! Thanks!

🙂

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 3

Easy one, thanks!

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

T.Ashish SSCarpal Tunnel Points: 4248 More actions · Answer 4

T.Ashish

SSCarpal Tunnel

Points: 4248

October 13, 2013 at 10:53 pm

#1658163

Good question Sasidhar

Mr. Kapsicum SSCertifiable Points: 6128 More actions · Answer 5

Mr. Kapsicum

SSCertifiable

Points: 6128

October 13, 2013 at 11:08 pm

#1658164

Very Easy Points 🙂

kapil_kk SSC-Insane Points: 21316 More actions · Answer 6

Carlo Romagnano (10/13/2013)
Clear and easy question! Thanks!
🙂

+1 🙂

_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

sqlnaive SSCoach Points: 17437 More actions · Answer 7

sqlnaive

SSCoach

Points: 17437

October 14, 2013 at 12:57 am

#1658172

Easy & good one. 🙂

Richard Warr SSCertifiable Points: 6966 More actions · Answer 8

I also got the answer correct but, seeing that 1/3 of respondents hadn't, clicked on "Discuss" to see if there would be something in here other than half a dozen people saying how easy they thought the question was.

As there wasn't, it's worth noting something the question got close to; the different way COMMIT and ROLLBACK work within nested transactions and making sure we understand why this is the case.

The discussion area gives us an opportunity to explore further some of the concepts raised by the original question in a way that might be of benefit to people coming in here having picked the incorrect answer.

SQLDoubleG Hall of Fame Points: 3100 More actions · Answer 9

Thanks for the question!

I personally find this link more illustrative than the provided one.

http://technet.microsoft.com/en-us/library/ms189336(v=sql.105).aspx

marlon.seton SSCrazy Points: 2623 More actions · Answer 10

I got this right because we'd been bitten on the ar*e by this when first amending our system to work with SQLServer as well as Oracle.

Gobikannan SSCrazy Points: 2735 More actions · Answer 11

Gobikannan

SSCrazy

Points: 2735

October 14, 2013 at 4:30 am

#1658225

Very easy one.

-----------------
Gobikannan

David Burrows SSC Guru Points: 65142 More actions · Answer 12

Nice question.

Due to the amount of criticism of previous QOD of the phrasing of the Q'a and A's I am surprised that no one posted anything about the wording of the answer!

It is technically incorrect as records are inserted into the table, they do not remain after the rollback.

Since the question asks for the result of the batch (although there are several bacthes) the answer should be 'no rows returned' or '0 Row(s) affected'

Please note I am not criticising the question or answer, just making an observation.

Far away is close at hand in the images of elsewhere.
Anon.

TaylorMade SSC Eights! Points: 967 More actions · Answer 13

If one of the choices were 1,2, I might have gotten tripped up.

ksatpute123 Hall of Fame Points: 3325 More actions · Answer 14

raulggonzalez (10/14/2013)
Thanks for the question!
I personally find this link more illustrative than the provided one.
http://technet.microsoft.com/en-us/library/ms189336(v=sql.105).aspx

+1.