I hope this is the right ng for sql serer 2005 express
I looked for guideline for optimal table design with regard to attribute
word boundary and other best practise, I failed to din any.


can anyone point me some quick guideline?

In some database, each attribute should ideally start on certain word
boundary otherwise penalty for either storage or performance will occur.

hi,
[quoted text, click to view]

actually you should not mess your logical modelling with the actual physical
implementation...
your physical design should match your logical one following related best
practices regarding normalization, keys evaluation and checks application...
as regard physical optimization, I'm aware of SQL Server can "optimize" up
to 8 bit columns for storage compliance with integers but this is usually
nothing worth digging into... you should instead consider your database's
compliance with the default collation of the system databases (the one
specified at install time), as some overhead is involved in tempdb for all
operations requiring tempdb usage (sorting, worktables, comparisons,
temptables ...) when a different collation is set for user database.. for
instance you usually should explicitely define collation of your temp tables
like
CREATE TABLE #temptable (
Id int NOT NULL,
Data varchar(n) COLLATE database_default NOT NULL
);
to avoid collation conflicts in comparisons when system databases has been
set with a different one as your user's database or use explicit collation
setting in comparison syntax like
SELECT <col_list>
FROM .... a, #temptb t
WHERE a.col = t.col COLLATE database_default

not a big issue, but worth considering..

I'd suggest
http://www.amazon.com/Server-2005-Database-Design-Optimization/dp/1590595297/ref=pd_bbs_1/102-5205181-8484932?ie=UTF8&s=books&qid=1174564505&sr=8-1
for a good one about design topic..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
--------- remove DMO to reply

Hello GS,

Take a look into 3rd normal form while designing your database model.THis
will help you reducing the storage and provide you better performance.
3 NF normalization is used to reduce the total amount of redundant data in
the database. The less data there is, the less work SQL Server has to
perform, speeding its performance.

http://defiant.yk.psu.edu/~lxn/IST_210/normal_form_definitions.html

Thanks
Hari

[quoted text, click to view]

How big is your database? How many simultaneous users? What have you done so
far to optimize performance? What indexes are in place? There are a million
questions that should be asked and answered before worrying about byte
boundaries. Any attempt to force these might actually degrade SQL Server's
ability to automatically optimize the physical data.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

[quoted text, click to view]