sql server - SQL Azure Friendly Database Versioning Idea -

i have number of identical sql azure databases clients need have versions tracked. sql azure in november of 2014 not support extended properties far know, if did extended properties tracking versioning changes done here:

http://wateroxconsulting.com/archives/versioning-in-your-sql-database#

i thinking of adapting concept making ddl trigger altered stored procedure held nothing versioning comments.

so question strategy - stored procedure best place keep kind of info, or there better place store textual versioning info in sql azure container? not want add table each database because dilute purpose of db , leaves room antics , need own care , feeding of table structure , etc.

and follow-up question tactics - best way alter procedure in tsql doing string manipulation append comment text?

thanks.

you seem asking how store some data in stored procedure, odd, because sql server fantastic tool storing data, not in stored procedures.

i'd better strategy create simple table store information mentioned in comment i.e.

create table dbo.databaseversion (     date datetime,     versionnumber decimal(5,2),     description narchar(40) ); 

and write additional row database on each ddl trigger.

i'd reasons have against pretty slim, perhaps create database schema metadata i.e.

create schema metadata; 

to make purpose of table clear , change "dbo." in ddl above "metadata." permissions can prevent antics, , if need care table structure far better first class data table unstructured comments in stored procedure.