|
Comments
|
|
Something that comes up for me from time to time is needing a user friendly record identity. My favored solution at present is to use an int Identity() but then present that value to the user base 36 encoded and decoding it when they provide it back. Do you have any best-practices for this need of an identity that is easy for a user to remember and to enter into an input form of some kind?
|
|
|
Can we go ahead and Change the SEED to a Value that is less than the highest number in the table. What would happen if we insert a new row. If that could have been explained it would be great. Btw, Thanks for such short videos.
|
|
|
It's nice video
|
|
|
You did not mention "not for replication" when setting the identity property.
|
|
|
Good demo Andy. However it would also be nice if resetting the identity is also shown in this demo. I know there are people who dont know that and can be interested into that. But overall, a fanstastic video.
|
|
|
detailed one. thanks.
|
|
|
Its nice. Hope it continued for few more minutes!
|
|
|
Muito Bom
|
|
|
Great basic stuff. It would be great to have a follow-up video on using identity columns (or not) in replicated database table scenarios.
|
|
|
Nice test after watching the video :D:D
|
|
|
I did not know that there was something called change script. Thanks; keep on the good work.
|