How many rules of normalization? 12. How many we are using? 3-5

And you are not saying that doctor Codd was developing useless 7 rules. The same point in article.

To show...

0 was there because I was thinking about 2 digit hours. Something like '01:36PM'. 

Oops, need change getdate to @datevar

IF (@dateformat = 7)

 begin

 set @converteddt =

  RIGHT('0' + right( convert(varchar, @datevar,100 ) ,7), 7)

  set @formatexists = 1

  end

IF (@dateformat = 8)

 begin

 set @converteddt =...

Formats you need based on your posted message:

IF (@dateformat = 7)

 begin

 set @converteddt =

  RIGHT('0' + right( convert(varchar, getdate(),100 ) ,7), 7)

  set @formatexists = 1

  end

IF (@dateformat = 8)

 begin

 set...

In reality, I have about 15 different formats. The one you asking looks:

IF (@dateformat = 8)

 begin

 set @converteddt =

  RIGHT('0' + CAST(DATEPART ( hh , @datevar ) AS VARCHAR(2)), 2) + ...

Thanks for email. In all my articles I am trying to show some ideas and provide with the example of the code (not necessary the best one but working). And...

#1. This function has a bug (or issue)

select dbo.fn_FormatDate (getdate(), 'xx:ss') will result 'xx:17'

It is not a date format. Function required format verification code.

#2. If every programmer will start...

You may be right, but unfortunately, we using extended properties for the applications. So, we already have 20-25 properties on each table (4-5 per column). To create some more (especially...

Sorry, previous post is mine as well

It is good if you have simple select. But with extended properties:

1. Change is more complicated

2. Flexebility is limited

If more complicated stored procedure...

As I pointed, it will be more than 999 number of records in a table.

Column data must be assigned automatically by the database. No one wants to rebuid the applications....

With binary conversion chances for the wrong result are smaller for the tables with 4+ columns. I was trying your method before I get proposed the other one. And actually,...

Same problem. Chances are very slim.

You may be right. I will try it. But the article was not written to show the best code, but to show the idea of how to use user defined function...

I didn't wrote the header. Sorry. You are right that there is no user defined function in SQL Server 7.

I can't use identity column. The column should be char(3) (or int with 3 digits). Database is growing dynamically. So, identity column has only 999 combinations. I need some where close...