All,

Has anyone created any kind of system for database maintenance using LLBLGen vs. the sysobjects/syscolumns tables?

I was just doing some scripting to implement audit fields on each table, and it occurred to me that it might be very easy using C#/LLBLGen code instead of writing it in SQL (it uses a lot of cursors, etc.).

Thoughts?

Phil

Other people may know exactly what you are talking about, but I'm a little lost . What are you trying to do? Could you post an example of what you are wanting to implement instead in LLBLGen.

bclubb wrote:

Other people may know exactly what you are talking about, but I'm a little lost . What are you trying to do? Could you post an example of what you are wanting to implement instead in LLBLGen.

Heh. Re-reading my original post, I wasn't very clear about what I was trying to do.

I often use SQL scripting against sysobjects and syscolumns to check whether all the tables in my database have certain columns. For example, in one project I wanted to make sure ALL tables had the following columns:

created_by_user_id created_date last_updated_by_user_id last_updated_date

Each time I created a series of new tables, I wanted an easy way to see which tables didn't have them, so I wrote scripts against the sys* tables to determine whether any of them were missing fields. I also write scripts to add the fields to the tables that didn't have them.

I can post some SQL code tomorrow (I don't have it handy) if that still doesn't make sense.

Anyway, I was thinking about creating views of those tables and mapping them to entities. The I could use dynamic queries to do this sort of maintenance. But that's as far as my thinking has gone since I thought if it right before the end of the day today.

Anyway, I was thinking about creating views of those tables and mapping them to entities. The I could use dynamic queries to do this sort of maintenance. But that's as far as my thinking has gone since I thought if it right before the end of the day today

I'd have done it the same way.

one shouldn't access sysobjects for this, INFORMATION_SCHEMA views are for this (which are filtered out by the sqlserver driver). Sqlserver 2005 has sys.* views for this. All filtered out by the driver. If you need them, either create a simple view which simply does a select * on these views or alter the driver sourcecode

Otis wrote:

one shouldn't access sysobjects for this, INFORMATION_SCHEMA views are for this (which are filtered out by the sqlserver driver). Sqlserver 2005 has sys.* views for this. All filtered out by the driver. If you need them, either create a simple view which simply does a select * on these views or alter the driver sourcecode

Cool! I didn't know about these views. I'll tinker around with them.

Thanks,

Phil