Thank you for your reply. I think this answers my question. In summary it appears that using a database that is too normalized would really affect cpu time. And in an age where disk is cheaper, it would be better to have some information duplicated vs. slowing the entire system down.
My pleasure, I hope you don't mind me rambling on about the importance of normalizing too much. It may eat away a bit of your time, but it's well worth the investment.
In summary it appears that using a database that is too normalized would really affect cpu time.
A database can't be "too" normalized. A "good" level of normalization would be BCNF[^]. That should give you a correct model, without (much) redundancy. Keep in mind that most RDBMS-es are optimized to work with relational data, in a relational format.
it would be better to have some information duplicated vs. slowing the entire system down
That sounds like a statement on optimization again
lnkPeopleType - many to many link between people and type (client can also pe a practitioner)
AddressType attribute on address (you may want multiple links if you need to have the same address for 2 types)
This is a heavily normalised structure and is a pain to use so create a view based on the PeopleType.
Never underestimate the power of human stupidity
I looked at the link you provided: It is not the same thing. The solution provided requires two select statements to return the same number of columns and the column types have to match. While in SQL server, you can have an arbitrary number of select statements and arbitrary data types.
i have configure the mail in sql server but when i am sending mail from sql server it is showing mail queue message but i am not getting the mail. i also grant the permission to msdb.dbo.sp_send_dbmail sp for public.
I am using SQL Server 2005 database.
I stored Thumb Image on two tables to the Image data type field.
When I compare these two images from both table is gives error...
"The data types image and image are incompatible in the equal to operator"
"Select FP1 From E_CH16APPLICANTS Where FP1 In (Select Photo From Tmp)"
I just like to verify that this Thumb Image is exist or not...
by using SQL Statement...
I'm no database expert at all, however I've never seen SQL code that compares big fields (blobs, images), and I expect that whenever you (think you) need it, you have a bad design to start with; there should be no doubt that the image, when present, is the right one (the only doubt I would allow for is whether the image is present at all); and IMO it would most always be wise to have a separate field that uniquely identifies the image (a hash or CRC would probably be fine).
The only way I know to compare two blobs/images is by using a programming language (say C#), fetch the two blobs and compare their elements in a loop.
Never use select *. As a shortcut, it leads to bad programming habits and it can lead to hard to find bugs as columns get renamed in the underlying database. You should always choose to explicitly select columns instead, partly because using
typically results in columns being retrieved that aren't needed in the result set.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be