I have seen nothing in the market that addresses this challenge, other than what was there four years ago when I originally built this system. We still use it at...

This is an awesome script. I am adding it to my box of scripts and putting a reference to this thread int he comment block so that I can't forget...

As noted by some of the other posters, the first time you modify anything after the trigger is installed, it will populate every report, data set and data source into...

Just an update since I originally wrote this article.

We have had this running on our main production SSRS instance since October 2011. It still works great and has saved our...

MM,

Thanks again for your efforts.

When I tested your latest solution against my enhanced group (from my previous reply), it didn't work.

I instead went a completely different way, which while...

Are you saying that any works order that has :

more than one occurrence of any single ItemCode, <-- in this case 101

and

that ItemCode appears in a Group <-- 101 appears...

MM,

WO #11 does have those codes, but it also has two 101s. That is the problem.

INSERT INTO [dbo].[WOs] ([WORowId], [WONum], [ItemCode]) VALUES (20, 11, '300')

INSERT INTO [dbo].[WOs] ([WORowId], [WONum],...

MM,

Thanks for your help.

The problem is that a given work order can't just have the codes at all, but must match quantity as well.

So WO #11 has the 101 code...

One thing that it seems I wasn't clear about. In the example WO #11 doesn't match, not because there are duplicate codes, groups that contain duplicates are valid. So, if...

Dale, you could put the version table in another database, but the trigger would still need to live in the ReportServer database. Since that is the case, you can't have...

In 2005, if you go to the Site Settings page and you have full admin rights on the server you should see a link for "Manage Jobs." If you then...

My problem is that this is live production data. I want to (if possible) have a way to keep the existing publications that feed the current environment up and running...

You can restrict the [Catalog].[Type] to 2 and 8 (RDL and RSD) and that should hopefully cut out on the non-compliant XML.

I agree that with SharePoint 2010 Enterprise you do have the option of using it to do version control. Sadly, we don't have that in our environment and with our...