Friday, March 30, 2012
Manage Triggers...
When I come in on Monday mornings - I would like to take a
quick glance to see if all the updates where done.
Thanks,
Lynn.
I was thinking there might be a modified column in the
Server Enterprise Manager - I do not see such a column.You can manage a table's trigger right-clicking on a table
in EM then All Tasks Then Manage Triggers...
If you need to take a look at all your triggers then you
can can use this script :
select object_name(parent_obj) TableName, name TriggerName
from sysobjects where xtype = 'TR'
>--Original Message--
>Is there one place where I can manage all triggers?
>When I come in on Monday mornings - I would like to take
a
>quick glance to see if all the updates where done.
>Thanks,
>Lynn.
>I was thinking there might be a modified column in the
>Server Enterprise Manager - I do not see such a column.
>.
>|||You mean you want to verify when a trigger ran? You can add the logic into
the trigger to store the date/time it ran into a modified column of the
table, if that is not what you are looking for, please reply.
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Lynn Pennington" <anonymous@.discussions.microsoft.com> wrote in message
news:000401c3d3a5$f5e891b0$a301280a@.phx.gbl...
> Is there one place where I can manage all triggers?
> When I come in on Monday mornings - I would like to take a
> quick glance to see if all the updates where done.
> Thanks,
> Lynn.
> I was thinking there might be a modified column in the
> Server Enterprise Manager - I do not see such a column.|||Ray.
Yes - I want to make sure the trigger ran.
So I add a datetime field to the table?
Thanks,
Lynn.
>--Original Message--
>You mean you want to verify when a trigger ran? You can
add the logic into
>the trigger to store the date/time it ran into a modified
column of the
>table, if that is not what you are looking for, please
reply.
>HTH
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"Lynn Pennington" <anonymous@.discussions.microsoft.com>
wrote in message
>news:000401c3d3a5$f5e891b0$a301280a@.phx.gbl...
>> Is there one place where I can manage all triggers?
>> When I come in on Monday mornings - I would like to
take a
>> quick glance to see if all the updates where done.
>> Thanks,
>> Lynn.
>> I was thinking there might be a modified column in the
>> Server Enterprise Manager - I do not see such a column.
>
>.
>
Wednesday, March 21, 2012
Making "incremental" updates to a data warerhouse
We have a legacy database whose data needs to be included in our yet-to-be-built sql 2005 data warehouse. Some of the tables don’t have any natural candidates for a primary key. (Of course, we also need to add other data to the mix.)
Suppose we load the empty warehouse initially. In following loads we don’t want to include those records that haven’t changed from the first load (“duplicates”) but we also don’t want to delete the contents of the entire warehouse because of the load time.Any ideas/best practices how to handle “incremental updates” to a warehouse would be appreciated.
TIA,
Bill
<<tables don’t have any natural candidates for a primary key>>
The above situation is likely a fundamental design flaw for which there is no easy fix. What is the usefullness and business meaning of an entity for which there is no natural key? It is likely nonsense.
However, from your definition of the problem, it sounds more like the key would be the combination of all columns in the row. How else would you define what is a "new" row vs. a "changed" row? Isn't that what you are describing? If so, there is your key.
Ken
|||You can use the Slowly Changing Dimension Wizard, an advanced transformation component, to create this type of process quite easily.
|||Can you explain how "slowly changing dimensions" can be used to create this type of process? (I'm new to this stuff and I can't make the connection on my own.)
TIA,
Bill
|||Here's a few references:
http://blogs.conchango.com/jamiethomson/archive/2005/06/06/1543.aspx (includes a demo)
http://sqljunkies.com/WebLog/tpagel/archive/2005/07/24/16195.aspx
Probably the best available reference is BOL.
-Jamie
Making "incremental" updates to a data warerhouse
We have a legacy database whose data needs to be included in our yet-to-be-built sql 2005 data warehouse. Some of the tables don’t have any natural candidates for a primary key. (Of course, we also need to add other data to the mix.)
Suppose we load the empty warehouse initially. In following loads we don’t want to include those records that haven’t changed from the first load (“duplicates”) but we also don’t want to delete the contents of the entire warehouse because of the load time.Any ideas/best practices how to handle “incremental updates” to a warehouse would be appreciated.
TIA,
Bill
<<tables don’t have any natural candidates for a primary key>>
The above situation is likely a fundamental design flaw for which there is no easy fix. What is the usefullness and business meaning of an entity for which there is no natural key? It is likely nonsense.
However, from your definition of the problem, it sounds more like the key would be the combination of all columns in the row. How else would you define what is a "new" row vs. a "changed" row? Isn't that what you are describing? If so, there is your key.
Ken
|||You can use the Slowly Changing Dimension Wizard, an advanced transformation component, to create this type of process quite easily.
|||Can you explain how "slowly changing dimensions" can be used to create this type of process? (I'm new to this stuff and I can't make the connection on my own.)
TIA,
Bill
|||Here's a few references:
http://blogs.conchango.com/jamiethomson/archive/2005/06/06/1543.aspx (includes a demo)
http://sqljunkies.com/WebLog/tpagel/archive/2005/07/24/16195.aspx
Probably the best available reference is BOL.
-Jamie
sql