> So if someone passes me a guid through a querystring, there no way
> that that will correspond to a database field on our database?
Nothing prevents one from using GUIDs as surrogate primary keys. It can
even be a convenient solution in case you want to expose those primary
keys in a web application without allowing users to easily "walk"
through a database table by incrementing/decrementing primary keys.
Re: identitycolumn as pk ...GUIDS would solve the problem i guess but i see different problems with ... What i want to do is insert the data in the new database... >> columns as primary keys is a commonly used technique so i bet there must ... Changing the database schema ultimately ... (microsoft.public.sqlserver.programming)
Re: interview questions ... the most important thing is that they understand database DESIGN.... There is no such thing as multiple primary keys in a ... Should an Autonumber field be used as a Primary Key? ...Normalization is a methodology or process for removing as much redundant ... (microsoft.public.access.tablesdbdesign)
Re: interview questions ... the most important thing is that they understand database DESIGN.... There is no such thing as multiple primary keys in a ... Should an Autonumber field be used as a Primary Key? ...Normalization is a methodology or process for removing as much redundant ... (microsoft.public.access.tablesdbdesign)
RE: Dataset.merge method ... and Deleted are matched on primary keys.... > from my database with another one that is filled with values from my active ... > My messed up display name ... > AGoodLastName... (microsoft.public.dotnet.framework.adonet)
Re: Updating the SQL key value ...Auto-numbered synthetic primary keys are the root of all evil. ... usually indicate a lazy approach to database design.... What if your database must be upgraded and the logic changes? ... I don't get it why you think of that as 'the root of all evil'.... (comp.lang.php)
