Viewing 9 posts - 1 through 9 (of 9 total)
Thanks Lowell
My thoughts almost exactly. I too would use a calculated field if it was required for an Index, but 90% of the time a bit of further analysis can...
May 20, 2010 at 9:05 am
OK Gaz - maybe the language was a bit intemperate. But I did feel that some of the comments were a little dismissive. We were ALL 'newbies' once - making...
March 2, 2010 at 4:32 am
Give the guy a break - this is aimed at newbies.
Right - it is a no-brainer for us grizzled database developers. I can add a little constructive criticism though Tim....
March 2, 2010 at 3:06 am
When I was a newbie to DB development (from a programmeer background) I liberally spread IDENTITY columns as PK. Simpler for me I thought and easier for the other developers.
Now...
March 1, 2010 at 3:14 am
Even for our local setup here in the UK it makes sense for most of our systems to use UTC (and I STILL think of it as GMT!). A lot...
February 26, 2010 at 2:36 am
James Stover (1/25/2010)
I would rather a table named tblCustomer than one named A72GZF (or something equally nonsensical).
So you've worked with Financial systems with 'Dynamic Table Creation' as well? Didn't...
January 25, 2010 at 5:14 am
Gail
I agree with you wholeheartedly. The only concession I would make would be UPPER CASE for table names - but that is more a matter of style and preference rather...
January 25, 2010 at 3:49 am
Hi all.
I'm one of those developers that write front ends to databases, and usually end up doing the database design as well.
I used to code in VB and...
January 25, 2010 at 3:34 am
Viewing 9 posts - 1 through 9 (of 9 total)