I had boss once, a VP, who was not all that bright and he would share his Outlook calendar; nothing wrong with that - we all shared our calendars (and kept some meetings private). The problem was that he would sometimes meet with other VPs and attach documents to those appointments that he intended to discuss. On a couple occasions he attached a spreadsheet with people's salaries (including his own). Once word got out pretty much everyone looked at it and It was a disaster, a complete disaster. It completely changed the dynamic in the office. Any animosity that existed between co-workers was magnified 10-fold.
I have always been against sharing salary information and this experience confirmed why it's a terrible idea.
Posting the salaries of public employees is fine because we, as tax payers, pay those salaries. Private company salary information should be always be private and employees should be discouraged from disclosing this info. I support that fully. It's nobody's business.
Edit: fixed errors, android auto-fix screwed me again.
-- Alan Burstein
Helpful links:Best practices for getting help on SQLServerCentral -- Jeff ModenHow to Post Performance Problems -- Gail ShawNasty fast set-based string manipulation functions:For splitting strings try DelimitedSplit8K or DelimitedSplit8K_LEAD (SQL Server 2012+)To split strings based on patterns try PatternSplitCMNeed to clean or transform a string? try NGrams, PatExclude8K, PatReplace8K, DigitsOnlyEE, or Translate8KI cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code. -- Itzik Ben-Gan 2001