K
Kyle Klaus
Hey Everybody,
I am working on re-creating a fairly weak Microsoft Access Application using
Visual Basic .NET and SQL server 7.0
basically the Access Database has been a Frankenstein project for a couple
years, so I'm looking to more or less just start over, starting with the
Database. What I'm looking for is any hints and tips that anybody has for
designing the database. I pretty much know all the tables I need. but I do
have a question about the keys for the tables.
reading another post in here from Marina, he mentioned: "I myself prefer
GUID's, because for inserting purposes, etc, they are easier to use since
you can create them on the client, and still know they will be unique." Now
I see that I can create an field in SQL Server that will use the value of
the row GUID.. is that what he meant, or did he mean that the key would
simply be a char (or similar) datatype large enough to hold a GUID and have
the client generate it using some utility?
Is that really beneficial.. I will have multiple people accessing the
database, about 10, but I doubt the concurrent users will ever be more than
2 or 3.
I also have a question about using types. Should I check the data strongly
before putting it into the database (so that the database is typed to
basicly hold anything you thow at it), or should I strongly type the
database and then catch errors if they occur?
Thanks Everybody, I'm just starting out with SQL Server, but I do have a
basicly understanding of it, and SQL in general
I am working on re-creating a fairly weak Microsoft Access Application using
Visual Basic .NET and SQL server 7.0
basically the Access Database has been a Frankenstein project for a couple
years, so I'm looking to more or less just start over, starting with the
Database. What I'm looking for is any hints and tips that anybody has for
designing the database. I pretty much know all the tables I need. but I do
have a question about the keys for the tables.
reading another post in here from Marina, he mentioned: "I myself prefer
GUID's, because for inserting purposes, etc, they are easier to use since
you can create them on the client, and still know they will be unique." Now
I see that I can create an field in SQL Server that will use the value of
the row GUID.. is that what he meant, or did he mean that the key would
simply be a char (or similar) datatype large enough to hold a GUID and have
the client generate it using some utility?
Is that really beneficial.. I will have multiple people accessing the
database, about 10, but I doubt the concurrent users will ever be more than
2 or 3.
I also have a question about using types. Should I check the data strongly
before putting it into the database (so that the database is typed to
basicly hold anything you thow at it), or should I strongly type the
database and then catch errors if they occur?
Thanks Everybody, I'm just starting out with SQL Server, but I do have a
basicly understanding of it, and SQL in general