Timeline for DB_ID context from farther up call stack
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 26, 2013 at 14:58 | answer | added | nabrond | timeline score: 4 | |
Dec 13, 2012 at 13:36 | comment | added | Joshua Honig | @SQLKiwi Question updated accordingly. Thanks for the other answer, too. I already have a variety of CLR functions for string manipulation, so this should be a natural next step for me. | |
Dec 13, 2012 at 13:35 | history | edited | Joshua Honig | CC BY-SA 3.0 |
added 393 characters in body
|
Dec 12, 2012 at 22:27 | comment | added | Joshua Honig |
Honestly I can't say I have an solid case for why this would be necessary. I found it very interesting and if I do figure it out I will put it in two handy little procs I use in my sandbox dev database: One that gets the full name of an object given the shortest recognizable fragment of the name (such as in my first example in the question), and another that kills objects by using the other function to get the full name and also uses type of the identified object to generate a DROP statement.
|
|
Dec 12, 2012 at 22:02 | history | tweeted | twitter.com/#!/StackDBAs/status/278983167711522816 | ||
Dec 12, 2012 at 21:55 | comment | added | Martin Smith |
It would be possible via extended events but only as a novelty really. Not something for serious production use. Even if you know the database name how would you use it anyway? Have everything in dynamic sql with a USE xyz; preceding it?
|
|
Dec 12, 2012 at 20:42 | history | edited | Joshua Honig | CC BY-SA 3.0 |
added 295 characters in body
|
Dec 12, 2012 at 20:21 | history | asked | Joshua Honig | CC BY-SA 3.0 |