Viewing 15 posts - 91 through 105 (of 129 total)
Not to knock batch file programming (there's some really impressive stuff you can do, lots of enthusiasts out there), but if this is a windows environment wouldn't VBScript (run using...
November 6, 2008 at 2:11 am
Sorry to whine, but this question is a little disappointing - It's educational on at least two counts (grouping sets - new feature, and possible gotcha on floating point numbers),...
September 23, 2008 at 2:22 am
ah-hah, thanks John, that makes a whole lot of sense!
August 15, 2008 at 5:57 pm
Hmm, getting late to this, but I'm having difficulty accepting the answer provided here. Here is the exact result I received on a SQL Server 2000 instance:
Server: Msg 245, Level...
August 15, 2008 at 4:43 pm
OK, so now I'm in awe of Chris Morris too... 🙂
August 5, 2008 at 6:03 am
wow, I am in awe (assuming it works 🙂 ). I would venture a guess that this is, indeed, the most efficient solution.
One fix required here is to separate the...
August 5, 2008 at 3:13 am
Hmm, my curiousity is piqued... The solution presented is quite interesting, but I believe the purported interest in bits and bytes is a little exaggerated, as the solution is still...
August 5, 2008 at 1:39 am
ah, thanks George! I wasn't planning on investigating further after Hugo's authoritative explanation, but I was a little weirded out that the BOL (2000) documentation I was looking at mentioned...
July 2, 2008 at 6:57 am
Hmm, I'm a little confused...
I assumed the question was talking about files from any arbitrary database - but the "ALTER DATABASE ... MODIFY FILE" clause can only (if I understand...
July 2, 2008 at 3:12 am
Hi, the sample actually assumes old-style ASP (usually coded in VBScript), but the point is not the extraction of the list of databases.
Getting the list of databases using this technique...
June 6, 2008 at 5:35 am
Hmm, I guess I knew where the author was going and got the answer right, but I disagree with the premise of the question.
The asssumption that you can prevent SQL...
June 6, 2008 at 4:07 am
I believe it is because Parameterization requires that every replaceable value in the query have its own "Parameter" in the cached plan.
So if the IN operator allowed for auto-parameterization (it...
April 17, 2008 at 3:00 am
Hi Ramkumar,
An "auto parameterized" query is a query that SQL Server caches and reuses a query plan for anyway, even though the query itself does not have any parameters defined.
eg,...
April 17, 2008 at 1:37 am
Viewing 15 posts - 91 through 105 (of 129 total)