4 weeks ago
We are having performance issues with EPIC's date function in where clauses due to UDF's in SQL server 2019.
Is it best practice to create a universe object or global variable. This is the function we are trying to define. EPIC_UTIL.EFN_DIN('t-1')
Request clarification before answering.
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.