Comments
Sort by recent activity
Hey Kendra, I'm GUESSING that one reason these Redgate surveys fall-flat with FoRG would be that a decent number of us work with multiple different groups/clients. In other words, these surveys are easy-ish to answer if I'm a DBA at, say, Acme Corp... but if I'm the de-facto DBA for piddlyCorp, weeble-wobbles Inc, a contractor for the Xyz Division of such and such corp, and a consultant for 3x 'Biggee' corps or whatever... then, I'm not sure exactly how to answer some of the very specific questions. Further, I'm typically going to have various/different responsibilities and/or ability to 'impact' overall direction from one company to the next... No idea HOW we go about fixing/addressing that (other than ... MAYBE it'd make sense for folks in this situation to, uhhhh, maybe take the survey a few times - once per each applicable client/role?) ... but assuming that this is PART of why response might be lower than expected... That said, I'll zip out and take it for 'one of' my clients right now... / comments
Hey Kendra, I'm GUESSING that one reason these Redgate surveys fall-flat with FoRG would be that a decent number of us work with multiple different groups/clients. In other words, these surveys are...
Jess, Did the licensing model for SqlPrompt (or maybe all RedGate tools) change somewhere along the way? For a LONG time, I didn't need to 'paste' licenses into SqlPrompt when activating the license ... instead, I simply needed to 'log in' to my account and my license would be applied automagically in the background. Strangely enough, it looks like installation of 10.x (and some subsequent updates/patches/etc.) appears to have done the following: - lost/removed previous licensing details (not too terribly surprising - I've gone from v9 to v10) - changed the entire licensing model - i.e., wasn't prompted to log in - I was prompted to paste a license key. Is this expected behavior? / comments
Jess, Did the licensing model for SqlPrompt (or maybe all RedGate tools) change somewhere along the way? For a LONG time, I didn't need to 'paste' licenses into SqlPrompt when activating the licens...
Perfect - glad to hear. (And no inconvenience, mostly just confused and/or wanted to make sure this wasn't some sort of bug/issue that Redgate wasn't somehow aware of. Sounds like everything is covered.) Thanks a ton Roseanna! / comments
Perfect - glad to hear. (And no inconvenience, mostly just confused and/or wanted to make sure this wasn't some sort of bug/issue that Redgate wasn't somehow aware of. Sounds like everything is co...
I use snippets very similarly to Tim - i.e., i don't much use the built-in snippets, but I do: - convert my own heavily re-used/re-issued 'commands' into scripts/snippets and - commonly 'interleave' SQL Prompt snippets with t-sql template paramters (i.e.,CTRL+SHIFT+M) - as that provides me with the 'idiomatic' syntax AND the ability to quickly/easily 'customize' or parameterize on the fly. And, when I say 'idiom' - I'm referring to how Ken Henderson used the term in his Guru's Guide to SQL Server Sprocs/etc. where his idea/goal of an 'idiom' was to find the most-correct and most-succinct version of a set of commands/directives. Or, in other words, if you look at how good 'scripters' work, they: - initially start by issuing commands 'manually' or 'from scratch' until they gain enough comfort and familiarity with the most COMMON ways those commands are used to address their needs then, - they save 'persisted' versions of those commands as SCRIPTS for easier re-use. Seems to me that Tim and I are using this functionality more as a tool to help us with 'scripting' than as a dev tool/aid (though there's no reason it couldn't be used in that sense - obviously). My thought/idea being that if Redgate were to host an 'official' repo full of snippets, a great guiding principle or idea for those snippets would be that: - they weren't just practical or 'time savers' - they were idiomatic - i.e., representing a 'best of breed' approach to tackling what's being done (easier said than done, obviously). And, if that were the case, it seems that such an endeavor/initiative would pair NICELY with current Code Analysis functionality and efforts. / comments
I use snippets very similarly to Tim - i.e., i don't much use the built-in snippets, but I do: - convert my own heavily re-used/re-issued 'commands' into scripts/snippets and- commonly 'interleave'...