ajsnyman (8/24/2011)

---

david.holley (8/24/2011)

---

...and you're thinking that the table that I posted was copied exactly from the DB? I fully understand. I was curious to see how you'd pull something like...

ajsnyman (8/24/2011)

---

Sorry man, it will reveal too much of our internal structure, which is commercial.

The basic structure:

- Create a cursor containing all the tables you want to create the trigger...

ajsnyman (8/23/2011)

---

Hi David,

We did the same type of auditing on a current project and it works great 🙂

We wrote a stored proc to generate triggers for all the tables requiring...

Sean Lange (8/23/2011)

---

Yeah that looks like a close enough skeleton that would work. However, I would suggest putting the presentation on the front end. Otherwise you will have to look...

I know that logic on the ASP.NET side can easily remove the data that remained the same, but is it possible for SQLServer to join the two records and the...

Sean Lange (8/23/2011)

---

Just my 2¢ but I think you will find a lot more issues down the road trying to parse this out column by column. It is incredibly difficult...

What did you mean by the statement "If you send stored procedure calls to the database, good on you." ?

The one nice thing about this is that all of the records in the child that exist in the parent can be updated en masse regardless if there's an actual...

My limited knowledge of SQL Server security somewhat grasps that concept given impersonation with ASP.NET. So I believe I understand the concept that doesn't matter who in the parent is...

Ok, not off topic, but addressing the larger issue and the reason for the original post...

The underlying problem is that I initially added a trigger on the table in the...

So I'm assuming that the records that exist in the parent DB can simply overwrite their counterparts in the child DB leaving any records unique to the child DB alone?

Is there any significant cost to having two views with more or less the same columns with just a few differences between the two?

The habit of using column (field) names is very ingrained into me. Using * honestly feels bad at this point. I was just curious not being entirely familary with SQLServer...

Right because for ever column you return that you don't need SQLServer is doing unneccessary work.

The issue with company and public holidays is certainly there. The current push is to get the basics out. We'll probably end up with a table for the holidays that...