Reputation
217
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 9
Newest
 Tumbleweed
Impact
~5k people reached

Nov
18
awarded  Tumbleweed
Nov
11
revised Composite Primary/Clustering Key vs GUID for Merge Replication scenario
deleted 1 character in body
Nov
11
awarded  Excavator
Nov
11
awarded  Editor
Nov
11
revised Sql Server merge replication primary key violations
expand shorthand to improve readability (took me a minute to figure out what -ve/+ve meant)
Nov
11
asked Composite Primary/Clustering Key vs GUID for Merge Replication scenario
Nov
11
suggested approved edit on Sql Server merge replication primary key violations
Jul
1
comment Any reason not to add 'rowversion' column?
Thanks for the confirmation. The note about the ROWVERSION values differing by subscriber is important to point out. It won't affect my architecture as it currently stands, but it's definitely worth keeping in mind for future development.
Jul
1
accepted Any reason not to add 'rowversion' column?
Jun
30
awarded  Yearling
Jun
30
asked Any reason not to add 'rowversion' column?
Nov
3
awarded  Notable Question
Dec
3
answered Access ODBC reserved error 7711
Oct
27
awarded  Popular Question
Jul
20
awarded  Scholar
Jul
20
accepted Column definition for a SQL Server equivalent to Access BOOLEAN type
Jul
19
comment Column definition for a SQL Server equivalent to Access BOOLEAN type
+1: I'll have to do some quick testing in my front end (MS Access) to see if the 1 vs -1 will be an issue for me. One thing that I have relied on in the past is doing an ORDER BY on a Yes/No column in Access. In ASC order that means the TRUE items show first then the FALSE ones. There may be other considerations as well, but your point about up to 8 BIT columns fitting in a single byte is well taken.
Jul
19
answered Column definition for a SQL Server equivalent to Access BOOLEAN type
Jul
19
asked Column definition for a SQL Server equivalent to Access BOOLEAN type
Feb
3
awarded  Self-Learner