Posts

Showing posts from December, 2016

65335 Factorial

459764383920613979883439418475912362779160654299904406543495500685046797388848736964674317913453992451139819075044220333120822685750055946841474872986908952589322695320079590690371483206782189890704226162956272896994211981001461378979390745734524821712568076248296842902896893962369929319969399080580676006008386192586237445206268751480677878228059609549720391925243526015745561716209423085452401958807920340913442186978520649930022799392596391489503705131425888416202671931608592011620851260776996498372998422311040190029280138309998154101753216950750768112446893193841933857983821467852878777504975026169177067196643126217306931069362247946491291701525699475228941940890043297973909595748306646537882550939900140506184062956878864156254524039818220069395281941412759902925593660204393793743266772368206938471133529260316431163227646619903411017538651337587020708004279782715013388122974517574232439329812006728335874641340882497219226800501142104505365763116566212906007742896967468634028170787126…

Beware the Errors of SSIS

Image
SSIS is a bit of a touchy subject where I work, and the more I use it, the more I sort of understand why.



While SQL Server is my background and I consider myself an expert in TSQL (not like, MVP level or anything), I don't do too much in SSIS. We have a home grown architecture which, in many ways, mimics functionality SSIS can do, and, for our purposes, usually works better and comes with fewer headaches. That said, there are some operations SSIS is simply hands down the best tool for the job. But I didn't come here to talk to you to day about when to or not to use SSIS. No dear reader, I come with a warning/complaint about how it surfaces error.

The description of how it surfaces errors is "not very well". It's undoubtedly something you get better at teasing out over time, but I think largely because of the breadth of systems it needs to interact with, surfacing meaningful errors for specific stages can often seem to have absolutely nothing to do with the error …

Big Crazy Linked Server Query

I got bored and was fiddling around with a statement I'd been doing manually in several steps to try to make it as easy to use (not read) and as quick as possible. The rundown is this:

    I have a query I want to run which spans two databases.

    The relevant schema for these two servers is as follows:


-- Server 1     -- Has about 500m rows     create table dbo.orders     (         order_id varchar(55) primary key clusterd,         Data varchar(8000) -- just a placeholder to show that there's other stuff in here     )     -- Server 2     create table dbo.orderLog     (         order_id varchar(55) primary key clustered,         PayloadId int unique,         OtherData varchar(8000) -- Placeholder for other columns.        --Not that it matters, but this data is different than the data on server 1     )     -- Has about 20 million rows     create table dbo.events     (         RecordId int identity(1,1) primary key clustered,         PayloadId int,         TriggerDate dateti…