181 reputation
10
bio website caspershouse.com
location Brooklyn, NY
age 39
visits member for 2 years, 5 months
seen 2 days ago

"Hi" and "thanks" are for the RW, not SO...

Obligatory social media links:

Twitter: @casperOne


Oct
9
comment Is it worth to update to an x64 environment?
Please edit this to be more constructive. Asking "worth it" is subjective at best. State your goals and what you are trying to achieve and then how moving to a 64 bit environment can help you achieve those goals.
Jun
24
awarded  Excavator
Jun
24
revised NULLs in a composite primary key - SQL Server
Added image with relationship diagram (user didn't have enough rep to do so himself).
Jun
24
suggested suggested edit on NULLs in a composite primary key - SQL Server
Jun
24
accepted Performing data update operations while backing up a large SQL Server database
May
16
asked Performing data update operations while backing up a large SQL Server database
Jan
5
comment Basic sql query problem
There's three questions here: 1) what is the effect of not indicating scope, 2) why you should choose one form over another and 3) performance issues when using a particular form. I'd recommend that the question be split up among these three lines and asked separately. That way, more concise answers can be given and then addressed separately
Dec
27
awarded  Talkative
Dec
1
awarded  Scholar
Dec
1
accepted Best type to use in a composite key when one of the values varies in type
Nov
21
awarded  Student
Nov
18
asked Would elasticsearch or RavenDB be better for fueling a statistics engine/random forest?
Nov
14
comment Best type to use in a composite key when one of the values varies in type
Both of which are not issues which I'm constrained on. I appreciate future-proofing, and I can't say this will never be a condition, but at the same time, I'm fairly confident for what I'm trying to do, this will not be an issue ever, or for a long, long time.
Nov
14
comment Best type to use in a composite key when one of the values varies in type
@JackDouglas: Yes; there might be some mining of these tables later for data, but this composite key will not be a part of that (it will be related to other data on other attributes).
Nov
14
comment Best type to use in a composite key when one of the values varies in type
I can appreciate the possibility of regretting it, but I can't understand it when the statement is so vague. Would you elaborate on why? What will a sql_variant as part of the key (given the updated information) do to post a problem?
Nov
14
comment Best type to use in a composite key when one of the values varies in type
Updated answer to reflect the non-query use of the key. It's not going to be used for anything really beyond the constraint.
Nov
14
revised Best type to use in a composite key when one of the values varies in type
added 190 characters in body
Nov
14
comment Best type to use in a composite key when one of the values varies in type
I'm not sure this is a good route for me; the goal of the structure is to be flexible enough to accommodate different ways that namespaces/domains identify their content. From what I can tell by the linked answer I have to have a table per data type I want to use as the natural key in the domain; what does this gain me except for many extra tables when a sql_variant does the same job? I've updated my question to reflect this (last item in the "other key facts setion").
Nov
14
comment Best type to use in a composite key when one of the values varies in type
The PostId is going to be used to uniquely identify a post within a namespace/domain, there will be a synthetic id generated as the primary key, this will be used for constraint/indexing purposes.
Nov
12
asked Best type to use in a composite key when one of the values varies in type