|
externel database reference collection
The boss man wants to reference PCs in NS and a different external SQL database ands server for the purposes of our migration efforts. Thing is, I'm not a huge SQL guy and I'm not quite sure how this should be done. Here are some ideas I had. - Create a linked server connection with a stored procedure to update a table on the same NS database
- Set up direct SQL calls in the collection configuration comparing the PC serial numbers
- Create an ODBC connection on the NS server to the other SQL server
I'm thinking option two will be the simplest, but is that possible? It would also be cooler b/c it would be real time. Any ideas and thoughts? Much of the information collected is going to be the same like hardware serial number and MAC addresses, so I don't think it would be hard to pare the two up. The goal is to give the deployment technicians the ability to right click on the PC(s) and deploy our migration job. The collections would tell us who doesn't have the Altiris agent on it yet and show who is yet to be migrated. There might be a simpler way to do this, but this is what the boss man wants.
Thanks,
masonje
__________________
The government's view of the economy could be summed up in a few short phrases: If it moves, tax it. If it keeps moving, regulate it. And if it stops moving, subsidize it.
- Ronald Reagan
|