Big Data: Cash Cow or Horsemeat?
The big data revolution seems to have failed to materialise, and for good reason - it's really difficult.
2013-02-18
223 reads
The big data revolution seems to have failed to materialise, and for good reason - it's really difficult.
2013-02-18
223 reads
The Term 'Big Data' is nothing more than a fad, and we'll soon be cringing with embarrassment at the thought that we ever used it. However, the data, and the challenges to processing it that it presents, will stay with us. If jargon like 'Big Data' helps us focus on the problems, then let’s use it: temporarily, perhaps.
2012-05-07
3,718 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
I wrote about this several years ago but will contribute again a life hack...
Hi I have this query that is slow during the 'not in' part of...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers