Discussion Locked
0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I asset manage the software for my company and am not technical, but in an effort to assist my monitoring duties I am trying to find a solution. We currently use SMS 2.0 reporting to a SQL database for inventory reporting and have found that "old" data never purges from our system which makes following up on license compliance very difficult. I understand that this is supposed to be fixed in SMS 2003, but we were told that this was fixed when upgrading from 1.2 to 2.0. Does anyone have any suggestions on a work around that was successful in their environment? I would like to pass this on to our technical team for possible implementation. I know there are add-on products, but with the continuing challege to cut costs, any cost-effective method/suggestion would be appreciated. Thanks-
2 replies
by m.a. durkee
I'm sure you've already read through all the documentation, but check out the MSDN link below - Item number 4, under the heading of SMS Database Maintenance.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsms/html/smsdb.asp
Hope it helps,
by m.a. durkee
Sorry, the address is:
http://msdn.microsoft.com/library/default.asp?url=/libra ry/en-us/dnsms/html/smsdb.asp
There shouldn't be a space in the word library...everytime I paste into this text box it places a space between the a and the r in library...
This discussion is closed to new replies.
Trending Software posts
Sort by Trending
Question Unanswered
Icons, favicons and merch graphics on Squarespace: my workflow for getting
0 helpful
0 replies
Discussion
Network Printer Works for Everyone Except Me
0 helpful
10 replies
0 helpful
4 replies
Discussion
Is There any Reverse Video Search Tool
0 helpful
8 replies
Discussion
Useful software Tip or Shortcut
0 helpful
0 replies