With Sql Server 2016 you’ll be able to store and return validated JSON from the database. Does this mean you can now consider using Sql Server as a back end to a Node.JS web server? Maybe: but before this becomes a reality you have several chambers to pass through
The JSON has landed (in beta at least) – and I think it’s now some practical use. I’ve collected a few technical references here. There may not be a native JSON type yet, but there are workarounds to provide the kind of assurance control-freak RDBMS developers find comforting. I’ve shown some of them in the […]
Some hand-matching of internal/external records may be needed even in an automated reconciliation. The matches will be stored in a database. Rules on matching can be enforced in the application, but there are often good reasons to place them in the database. In Sql Server, a filtered index (with a WHERE clause, in this case […]
You never solve problems, only exchange them for new ones. Usually they’re just new to you, but cloud computing “update risk” actually looks NEW.
Indexes often double as constraints. Each combination of values must only appear once among the columns of an index defined as UNIQUE. The “filtered” index allows some refinement. Suppose that in one column you won’t allow a specific value to appear more than once, but you don’t mind other values being duplicated. A good example […]
Well, not literally – these are features I tend to overlook because I don’t often need them. If you’re the same, this may be helpful. It isn’t a complete list (I’ve forgotten the others) but I’ll try to add to it as things come to mind.
In Manager’s List of Potential Cloud Computing Benefits I promised to write up a list of risks, so here it is. The question probably isn’t “should I use cloud services or not?”, but “which activities and data would be safe to migrate to the cloud?”. You’ll have thought of most of these; if you see […]