My Place For SQL

It looks abnoxious when as MS MVP I advocate MOF/MSF Database Designs for customers and USers but still one of our main System Databases named MSDB has columns which are related to Datetime have been kept as INT...

WHo Designed this Database and WHo pruned it... I wish to meet them .. God... It wasted my extra time and Extra resources to get them casted , So that my RDL can just  publish the report on SYSJOB and SYSJOB HISTORY..

RUN_DATE and RUN_TIME why are they int  type  ?? By any standard both should have been Datetime Types.

It is not a BUG but a Flaw in Database Design Understanding???

It has been long time that I am back on my Blog... But trust me I missed it more than it might have missed me..

Okay here is a kwel  finding.. For those who are confused about Guest account in SQL server Databases..

Well we need GUEST account in Master and TEMPDB  ...  because when when we create login that person should get authenticated at least w.r.t Public Profile..  then onwards  suppose if he/she hasnt been added to any Database then he will keep on looking at Master DB from Public profile with no rights or rights conferred on Guest  Account.

IS IT A SECURITY THREAT? Partially  yes .. I feel so thats why I deny permission on all SYS OBJECT in these two Databases for Guest Account..  but it is mandatory to keep Guest account we cant remove it...

I wish Microsoft comes out with some other model and GUest account is taken off  because it effects DBAs thought process more than it effects my SQL Server