Printing the String

Question

Printing the String

Steve Jones - SSC Editor

SSC Guru

Points: 736173
More actions
September 20, 2019 at 12:00 am

#3674533

Comments posted to this topic are about the item Printing the String

Viewing 9 posts - 1 through 8 (of 8 total)

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

Stewart "Arturius" Campbell SSC Guru Points: 72624 More actions · Answer 1

Nice question, thanks Steve

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”

Japie Botma SSCrazy Points: 2990 More actions · Answer 2

Does it make sense to put USER_NAME() in the script? I think no and that is why 31% picked the second answer. 🙂

5ilverFox
Consulting DBA / Developer
South Africa

Sean Lange SSC Guru Points: 286590 More actions · Answer 3

Good question but imho the best answer was not on the list of choices. It would be better to use ORIGINAL_LOGIN() instead of USER_NAME().

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

Shayn Thomas SSCertifiable Points: 5863 More actions · Answer 4

Agreed,

Wouldn't user USER_NAME() for this purpose

Thanks for the question though

---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know

srienstr SSCrazy Points: 2435 More actions · Answer 5

Sean Lange wrote:

Good question but imho the best answer was not on the list of choices. It would be better to use ORIGINAL_LOGIN() instead of USER_NAME().

It seems to me that the user name is going to be more frequently a useful piece of information.

That said:

IF ORIGINAL_LOGIN()=USER_NAME()

PRINT 'This action was initiated by ' + USER_NAME() + ' and it failed.'

else

PRINT 'This action was initiated by ' ORIGINAL_LOGIN() + ' as ' + USER_NAME() + ' and it failed.'

Puto me cogitare, ergo puto me esse.
I think that I think, therefore I think that I am.

Japie Botma SSCrazy Points: 2990 More actions · Answer 6

Hmmm, that would still not make sense. Why would you want your own name displayed during debugging? Don't know your own name? 🙂

5ilverFox
Consulting DBA / Developer
South Africa

Sue_H SSC Guru Points: 90860 More actions · Answer 7

It's useful when doing some things using EXECUTE AS, reverting etc and you want to check which user context is in place at what point in the process.

Sue

Steve Jones - SSC Editor SSC Guru Points: 736173 More actions · Answer 8

The best answer is the one that the question asked, which isn't an architectural question on the function usage, but rather, how to PRINT strings.