THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is AndyLeonard.blog.

BimlExpress Metadata Framework

This blog has moved! You can find this content at the following new location:

http://andyleonard.blog/2017/01/31/bimlexpress-metadata-framework/

Published Tuesday, January 31, 2017 5:00 PM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Chris Taylor said:

Hi Andy,

do you have any indication as to when Varigence will fix the "Object reference not set to an instance of an object" bug in BIMLExpress as per: https://www.varigence.com/Forums?threadID=9625

I'm not sure what differences you have in your BIML code which makes your scripts work but for myself and many others a master/child package setup doesn't work.

regards,

Chris

March 6, 2017 6:33 AM
 

andyleonard said:

I know the good people at Varigence are working hard on the next release. Like Earnest and Julio Gallo, they will release no software before its time. Hang in there, sir.

:{>

March 6, 2017 11:47 AM
 

Asbjørn said:

Hi Andy,

Thanks a lot for making this framework public. I downloaded it and have it running in our dev environment and the tests look very promising. Before I go ahead and create my own stored procedures to fill in meta-data, may I ask how you usually go about it? One approach as I see it is to manually fill in metadata just at the connection and database level and then have a SSIS package grab metadata for all tables/views/columns in the source to populate the other metadata tables. Then one could just use an update script to set the GenerateBimlFlag's for the tables needed and a trigger or sp to set the lower level flags. Of course one would still have to manually update the configurables (for example IsColumnBusinessKey) but most of the metadata would generate automatically.

Another approach would be to import all neccessary tables once and then use those tables to generate all metadata at the table level or lower. So instead of reading metadata from the source it would be read at the destination.

I guess you use the RefreshMetadata flag to hint at your metadata-flow on which metadata should be updated and which should stay static, but I haven't seen where you reference it - is your own metadata flow publicly available?

Sorry if the above was a bit unstructured but am just getting started with BIML and am very excited :)

Best regards,

Asbjørn

August 21, 2017 6:37 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

News

My Latest Book:

Community Awards



Friend of Red Gate

Contact Me

Archives

Privacy Statement