Patterns for table design

I am looking for something similar to patterns for table design, but I have been unable to find anything on that, or good rule of thumb performance guides for table design.

Most of the situations we face look like perfect candidates for patterns, and some good rules of thumb -- problems like scalable OLAP requirements PLUS real time reporting.

I am looking for several differnet approaches and a good summary of the trade-offs for each one.

Thanks!

You're in luck...the newest book in the Martin Fowler Signature Series is on Database Refactoring

http://martinfowler.com/books.html#refactoringDatabases

I haven't read it yet but looking at the website (that has a catalog of the patterns), it seems to be pretty thorough. It goes hand in hand with Martin's Patterns of Enterprise Application Architecture and the other book in the series on Enterprise Integration Patterns.

Password History in SQL Server

I know that there is a rule in SQL Server password naming that last n number
of password cannot be used. Can anyone tell me how much is this n?
Thanks in advanceHi
SQL Server 7.0, 2000 and 2005 do not keep password history.
If you have a need for this, use NT Integrated Security and then that is
done at AD level.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SRV" <SRV@.discussions.microsoft.com> wrote in message
news:CB0A689E-7AB6-47FA-AADD-8F774F390974@.microsoft.com...
>I know that there is a rule in SQL Server password naming that last n
>number
> of password cannot be used. Can anyone tell me how much is this n?
> Thanks in advance
>|||> SQL Server 7.0, 2000 and 2005 do not keep password history.
Mike, I believe SQL 2005 indirectly provides a password history policy under
Windows 2003 when with the CHECK_POLICY option is ON. SQL Server calls the
Windows NetValidatePasswordPolicy API to enforce local server password
policies.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uJZeRYw5FHA.2984@.TK2MSFTNGP14.phx.gbl...
> Hi
> SQL Server 7.0, 2000 and 2005 do not keep password history.
> If you have a need for this, use NT Integrated Security and then that is
> done at AD level.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "SRV" <SRV@.discussions.microsoft.com> wrote in message
> news:CB0A689E-7AB6-47FA-AADD-8F774F390974@.microsoft.com...
>|||That is right: On Windows 2003, SQL Server 2005 can enforce the Windows
password policy. The password history length is determined by the Windows
policy in that case. You can display the policy settings by running
secpol.msc.
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan Guzman" wrote:

> Mike, I believe SQL 2005 indirectly provides a password history policy und
er
> Windows 2003 when with the CHECK_POLICY option is ON. SQL Server calls th
e
> Windows NetValidatePasswordPolicy API to enforce local server password
> policies.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uJZeRYw5FHA.2984@.TK2MSFTNGP14.phx.gbl...
>
>