Timeline for Finding the Table and Column Based on a Known Value
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 10, 2014 at 5:55 | history | tweeted | twitter.com/#!/StackDBAs/status/509580966873300992 | ||
Sep 9, 2014 at 21:23 | vote | accept | Hammer Bro. | ||
Sep 9, 2014 at 20:56 | answer | added | Aaron Bertrand | timeline score: 3 | |
Sep 9, 2014 at 20:34 | comment | added | Hammer Bro. | While it's still technically running, I think I've already found one of the fields that I want and some more tables of interest besides. @AaronBertrand -- think you could type up (or even copy/paste) your solution into an answer here so it's obvious for future string-searchers. Thanks. | |
Sep 9, 2014 at 18:33 | comment | added | Aaron Bertrand | You can even limit it to string columns that are large enough to actually contain your value. | |
Sep 9, 2014 at 18:31 | comment | added | Hammer Bro. | @AaronBertrand That looks promising. I'm running it for a known value now while I try to understand more than generally how it works, but it's got the essence of what I want to do -- search every string column on every table for a particular value. I don't think such brute-forcing could be done faster. | |
Sep 9, 2014 at 18:14 | comment | added | Hammer Bro. | @MaxVernon No, most of them are likely VARCHAR, like 'HB194' or 'Immediately'. | |
Sep 9, 2014 at 18:05 | comment | added | Hannah Vernon♦ |
That value you show in the question is typically referred to as a GUID, or Globally Unique Identifier (uniqueidentifier in SQL Server parlance). Are all the values you looking for a GUID?
|
|
Sep 9, 2014 at 17:49 | review | First posts | |||
Sep 9, 2014 at 18:04 | |||||
Sep 9, 2014 at 17:47 | history | asked | Hammer Bro. | CC BY-SA 3.0 |