Viewing 15 posts - 211 through 225 (of 581 total)
You want to present the results in a format QA isn't really equipped to deliver. You could do it, perhaps using a t ble valued function and some dynamic sql...
June 22, 2006 at 8:33 am
Not so fast! I agree the solution is workable and suitable (unavoidable) for some situations. Problem-solvers prefer situations with awkward or unusual constraints. It means we have to use ingenuity and makes things more interesting. But...
June 22, 2006 at 7:07 am
But in any form of SQL, if you have a group by clause, any column in the select list must either be enclosed in an aggregate function, or must also...
June 21, 2006 at 6:53 pm
IN will only accept literals i.e. the actual values spelled out right there between the brackets(). You could, but almost certainly shouldn't, use dynamic SQL to get the literals between...
June 21, 2006 at 4:52 pm
Are you saying that a domain of {0,1} or {'T','F'}, or whatever, in the logical model should never be mapped to the semantic values true, false in the conceptual model...
June 21, 2006 at 4:38 pm
I'm not sure whether a stored proc would be approriate for your situation, but if so:
June 21, 2006 at 4:16 pm
More of a piccalilli man myself...and brown sauce. English food is objectively disgusting, but when you're raised on it you can't help liking it, and in a perversely defiant way...
June 21, 2006 at 3:09 pm
To send a recordset to the DB, you would preferably use an update method. The recordset (even if empty) should have come from the DB to start with, so you are...
June 21, 2006 at 2:50 pm
I can't see what ordering algorithm you want to use. Position in what sequence?
June 21, 2006 at 2:38 pm
Agree that meaningful grouping of columnname prefixes is almost certainly symptomatic of denormalisation. Might not be a business problem though.
June 21, 2006 at 2:31 pm
Then we're all agreed. The data should be stored in classical relational form (subject to SQL compromises), for all the (one hopes) obvious reasons. The only (mildish) dispute, certainly from...
June 21, 2006 at 2:27 pm
I still say that unless the relevant part, logical physical and temporal, of your system is read-only, sometimes reads using NOLOCK will be plain wrong, unless by lucky accident. This is true...
June 21, 2006 at 2:10 pm
Dead quick to write, dead slow to run and debug (+ scalability to >8000char, embedded commas?). Admin procedures are allowed to be slow (if necessary), production ones aren't (it shouldn't be necessary). It...
June 21, 2006 at 1:56 pm
The only way to do it as a single NOT IN subquery would be to concatenate the columns. But unless you use indexed calc columns, and probably even then, this...
June 21, 2006 at 1:21 pm
Build your string first and use it as part of the spec of your DTS package. You should be able to create the package in TSQL, and incorporate the string...
June 21, 2006 at 11:12 am
Viewing 15 posts - 211 through 225 (of 581 total)