Comments
Sort by recent activity
Have you tried the redgate.uservoice.com ? / comments
Have you tried the redgate.uservoice.com ?
Hi @krzysztofkroczak I would like to have it like this: COALESCE(
ns.com_all_A0
, ns.com_all_A1
, ns.com_all_A2
, ns.com_all_A3
, ns.com_all_A4
, ns.com_all_A5
, ns.com_lastyear_A0
, ns.com_lastyear_A1
, ns.com_lastyear_A2
, ns.com_lastyear_A3
, ns.com_lastyear_A4
, ns.com_lastyear_A5
, ns.com_lastmonth_A0
, ns.com_lastmonth_A1
, ns.com_lastmonth_A2
, ns.com_lastmonth_A3
, ns.com_lastmonth_A4
, ns.com_lastmonth_A5
, ns.com_lastweek_A0
, ns.com_lastweek_A1
, ns.com_lastweek_A2
, ns.com_lastweek_A3
, ns.com_lastweek_A4
, ns.com_lastweek_A5
, ns.com_lastday_A0
, ns.com_lastday_A1
, ns.com_lastday_A2
, ns.com_lastday_A3
, ns.com_lastday_A4
, ns.com_lastday_A5
currently I get it like this after formating:
COALESCE(ns.com_all_A0, ns.com_all_A1, ns.com_all_A2, ns.com_all_A3, ns.com_all_A4, ns.com_all_A5, ns.com_lastyear_A0, ns.com_lastyear_A1, ns.com_lastyear_A2, ns.com_lastyear_A3, ns.com_lastyear_A4, ns.com_lastyear_A5, ns.com_lastmonth_A0, ns.com_lastmonth_A1, ns.com_lastmonth_A2, ns.com_lastmonth_A3, ns.com_lastmonth_A4, ns.com_lastmonth_A5, ns.com_lastweek_A0, ns.com_lastweek_A1, ns.com_lastweek_A2, ns.com_lastweek_A3, ns.com_lastweek_A4, ns.com_lastweek_A5, ns.com_lastday_A0, ns.com_lastday_A1, ns.com_lastday_A2, ns.com_lastday_A3, ns.com_lastday_A4, ns.com_lastday_A5)
Thanks, / comments
Hi @krzysztofkroczak I would like to have it like this:COALESCE(
ns.com_all_A0
, ns.com_all_A1
, ns.com_all_A2
, ns.com_all_A3
, ns.com_all_A4
, ns....
I have the same issue. And it always happens when I have a large resultset in the result tab.
After closing the query tab everything works again.
No more out of memory error. (Im using SSMS v17.2 - 14.0.17177.0) / comments
I have the same issue. And it always happens when I have a large resultset in the result tab.
After closing the query tab everything works again.
No more out of memory error. (Im using SSMS v17.2 ...
I've got the same problem. :shock:
Any info when this issue will be fixed?
(I'm using Microsoft SQL Server Management Studio - 13.0.16105.4 - Version 16.105.4) / comments
I've got the same problem. :shock:
Any info when this issue will be fixed?
(I'm using Microsoft SQL Server Management Studio - 13.0.16105.4 - Version 16.105.4)