i guess i'm hooked because here i am again writing about this stuff. anyway, this was just too cool to pass up. using one line, you can compare two text files:
compare-object $(get-content file1.txt) $(get-content file2.txt)
didn't say the stuff was complicated. :)
UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress. if you are using the v2 toolkit, PLEASE read this blog post before proceeding. here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
I am trying to compare two files with about 20,00 entries each and it doesnt seem to work. If I compare them in Access, I get 1700 differences. When I compare with Powershell, about 20,00 differences.
ReplyDeleteIs there a limit to the amount of data that can be compared?
There does appear to be a default limit. Check out: http://dmitrysotnikov.wordpress.com/2008/06/06/compare-object-gotcha/
ReplyDeleteHe writes about how to get around the limitation.
you know, i had JUST read that same article earlier this week and meant to go make a comment. thanks garth!
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDelete