Timeline for How to Convert Data to Proper Case In SQL Server
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15 at 14:16 | history | protected | CommunityBot | ||
| Jul 24, 2018 at 6:04 | history | tweeted | twitter.com/StackDBAs/status/1021637339108581376 | ||
| Mar 2, 2017 at 21:38 | vote | accept | SQL_Deadwood | ||
| Mar 2, 2017 at 21:37 | history | edited | SQL_Deadwood | CC BY-SA 3.0 |
updated content
|
| Mar 1, 2017 at 20:43 | answer | added | billinkc | timeline score: 17 | |
| Mar 1, 2017 at 4:26 | answer | added | Hannah Vernon♦ | timeline score: 7 | |
| Feb 28, 2017 at 23:31 | comment | added | SQL_Deadwood | I agree this problem isn't well suited to T-SQL but the source of data is Excel and PeopleSoft. The Excel workbooks have no real rules governing them (no LOVs, for example). The PeopleSoft data relevant to this function is all uppercase. The destination app is Workday, which I'm told does not handle data presentation as one would expect. With no other option but cleansing the data in SQL Server, we went ahead with this solution. We have separate tables for the imported data and combined data. This project has been a great example of why IT needs to be involved from the beginning. | |
| S Feb 28, 2017 at 18:31 | answer | added | SQL_Deadwood | timeline score: 3 | |
| S Feb 28, 2017 at 18:31 | history | asked | SQL_Deadwood | CC BY-SA 3.0 |