MS SQL: Bad Ju-Ju Magic

I call for a vote of no confidence... Running the statement select count(*) from BagLocations returned the value 19 014 584. Then I started the following query: insert into BagLocations_JuganTemp select * from BagLocations Then, while that was running (it ultimately took 6:33), I ran select count(*) from BagLocations which returned about 3 000 000. Then, once the long-running query completed, I ran select count(*) from BagLocations which returned 19 014 584 again, as did select count(*) from BagLocations_JuganTemp. Ju-ju bad. Verry ba...

Read More

Trump card

Eugene's response to this post is one of the most amusing refutations I have ever seen on the net. I won't steal its thunder by quoting, just give it a read if you have 30 seconds to spa...

Read More

MS SQL: Functions and Procedures

Functions and procedures in MS SQL 2000 don't play particularly well together. That's not really a problem, seeing as they both solve the same problem: running a sequence of operations. But (and this is a particularly large but) functions offer only a subset of the range of operations available — most notably, they can't alter data in tables or create temporary tables. So why would anyone use a function? They're particularly useful as they can return values. Unlike stored procedures which return an error-code and can pack output variables...

Read More

Tentatively the mind enters another expression spa...

Read More