BINARY_CHECKSUM usually used to detect changes in a row. If any row has any value changed, this function can be used to figure out if the values are changed in the rows.
However, if the row is changed from A to B and once again changed back to A, the BINARY_CHECKSUM cannot be used to detect the c...
@ypercubeᵀᴹ Very interesting indeed. I wonder have Google provided any funding to the PostgreSQL Global Development Group - and also, have Amazon with their Babelfish project? The latter is still in "coming soon" mode - and I'm willing to bet (gentelmen's) that it will not appear by the end of the year!
@McNets bidn.com needs updated to the web archive link (above). msdn doesn't strictly need the update i guess but i was going to update it the docs.ms page it redirects to
@CadeRoux Took us a while, but we're finally getting there - temps in the low-mid 60s (15C) for the next week or two (which is still pretty warm for this time of year)
I would think that this would be a fairly simply question, but I've actually had a difficult time finding an answer for this.
The question:
Can you move rows of data within a partitioned table from one partition to another by simply updating the partition column so that it crosses the partition ...
Yeah, so how is the table partitioned (in this answer)?
I see the other answer by Jason Halladay and it creates the table, creates the function and then adds the clustering index using the partititioning function. So that looks ok.
If string_expression input is of type varchar(max) or nvarchar(max), REPLICATE truncates the return value at 8,000 bytes. To return values greater than 8,000 bytes, string_expression must be explicitly cast to the appropriate large-value data type.
"Why is this database not 200GB like I am putting 3m rows in and 250k of them are supposed to have 400KB made up nvarchar(max) blobs in them?"
