Timeline for Only SQL Server Enterprise Edition supports compression - how to work around that?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2019 at 9:28 | vote | accept | Marcello Miorelli | ||
| Apr 29, 2019 at 9:04 | comment | added | Martin Smith |
What you probably saw is the script getting an error and the error message being buffered and then it going onto another long running statement that didn't return anything to the client so the error message stayed buffered then when you cancelled the query the packet was finally sent to the client. e.g. As RAISERROR ('Some error message', 16,1);WAITFOR DELAY '23:59:00'
|
|
| Apr 29, 2019 at 8:26 | comment | added | eckes | If this is such a small table there is not much need for bothering with compression anyway, just remove the data_compression clause. | |
| Apr 29, 2019 at 8:20 | comment | added | Marcello Miorelli | Exactly, I agree, and that's exactly why I've put all the story in. It uses your sp_ineachdb by the way. | |
| Apr 29, 2019 at 0:56 | comment | added | Aaron Bertrand | I don't think your script "went on forever" because the feature wasn't supported on that edition. That error message should have been returned immediately, not after canceling. | |
| S Apr 28, 2019 at 21:22 | answer | added | Marcello Miorelli | timeline score: 1 | |
| S Apr 28, 2019 at 21:22 | history | asked | Marcello Miorelli | CC BY-SA 4.0 |