jnelson993
Posts: 899
Score: 127
Joined: 2/18/2005
From: Minneapolis, MN
Status: offline
|
I don't think that's a fair assessment. When a machine gets deleted from the regional sites, they're gone from there, and yes, it's true that they don't get deleted from the central site...however, if you set up the delete aged and delete obsolete maintenance tasks, they will be removed. But here's a key piece of information, IN ADDITION to that, the fact that they've been deleted DOES in fact trickle up. They don't get removed from the DB, but they do get a DECOMMISSIONED flag. So if you want to exclude machines that have been deleted from the regionals from showing up on the central, then change your collection queries to check for DECOMMISSIONED = 0.
Here at Wells, we have a central reporting site that aggregates all the SMS data from all the regional sites and sites from other Wells-owned companies. We don't want to keep stuff older than 30 days in those sites, but for auditing and other purposes we have a mandate to keep stuff at least 60 days up in the reporting site. So deletions happen at regional sites, and that fact trickles up by flagging those machines as decommissioned. If we exclude decommissioned machines, we only have valid machines.
If we can rely on our central reporting site with hundreds of thousands of clients and hundreds of servers all replicating up to it, then you should be able to as well.
You want to see all of your deleted regional machines? Run this SQL query from the central/reporting site:
SELECT *
FROM dbo.v_R_System
WHERE Decommissioned0 = 1
You want to only see valid machines? Run this:
SELECT *
FROM dbo.v_R_System
WHERE Client0 = 1
AND Obsolete0 = 0
AND Decommissioned0 = 0
_____________________________
Number2 (John Nelson)
MyITForum - Blog
MyITForum - Forum Posts
|
Printable Version
All Systems collection not updating on Central Primary ... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread