|
101 KB
|
121 KB
|
23 KB
|
51 KB
|
144 KB
|
87 KB
|
227 KB
|
219 KB
@funfun: pls see this comment from Ivan: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/9543?tab=comment#89556DCF-7F18-97F5-E858-D3F3D1ACAE8B
The root cause is execution of "DBCC SHRINKDATABASE(N'database_name')" via CommonSchemaUtil.executeDDL()
generates the following warnings:
java.sql.SQLWarning: Changed database context to 'database_name'. java.sql.SQLWarning: DBCC SHRINKDATABASE: File ID 1 of database ID 13 was skipped because the file does not have enough free space to reclaim. java.sql.SQLWarning: DBCC SHRINKDATABASE: File ID 2 of database ID 13 was skipped because the file does not have enough free space to reclaim. java.sql.SQLWarning: DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Hence, CommonSchemaUtil.executeDDL()
returns 'false' to caller (CommonSchemaDialog) which cannot distinguish 'warning' from 'error' and thus simply displays a message dialog and reports "CommonSchemaUtil.executeDDL() was not successful.".
The root cause is execution of "DBCC SHRINKDATABASE(N'database_name')" via CommonSchemaUtil.executeDDL()
generates the following warnings:
java.sql.SQLWarning: Changed database context to 'database_name'. java.sql.SQLWarning: DBCC SHRINKDATABASE: File ID 1 of database ID 13 was skipped because the file does not have enough free space to reclaim. java.sql.SQLWarning: DBCC SHRINKDATABASE: File ID 2 of database ID 13 was skipped because the file does not have enough free space to reclaim. java.sql.SQLWarning: DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Hence, CommonSchemaUtil.executeDDL()
returns 'false' to caller (CommonSchemaDialog) which cannot distinguish 'warning' from 'error' and thus simply displays a message dialog and reports "CommonSchemaUtil.executeDDL() was not successful.".
Also check the DBCC action.
MssqlDBCCDialog will not display an error dialog and reports "CommonSchemaUtil.executeDDL() was not successful."; instead, the generated warning messages is displayed in Messages tab owned by MssqlDBCCDialog. This behavior is the same as the fix made for issue #7059
Also check the DBCC action.
MssqlDBCCDialog will not display an error dialog and reports "CommonSchemaUtil.executeDDL() was not successful."; instead, the generated warning messages is displayed in Messages tab owned by MssqlDBCCDialog. This behavior is the same as the fix made for issue #7059
@Sachin,
MssqlDBCCDialog and AlertDialog (issue #7059) are derived from CommonSchemaTab, MssqlShrinkDatabaseDialog
is derived from CommonSchemaDialog
. I will modify MssqlShrinkDatabaseDialog
and CommonSchemaDialog
to let them behave similar to MssqlDBCCDialog/AlertDialog and CommonSchemaTab. This means:
(1) A Messages tab will be added to MssqlShrinkDatabaseDialog to display warning messages.
(2) OK button will be disabled after warning messages are displayed in Messages tab.
(3) MssqlShrinkDatabaseDialog will remain open after warning messages are displayed, user needs to close it manually.
If you have different thoughts, please let me know.
@Sachin,
MssqlDBCCDialog and AlertDialog (issue #7059) are derived from CommonSchemaTab, MssqlShrinkDatabaseDialog
is derived from CommonSchemaDialog
. I will modify MssqlShrinkDatabaseDialog
and CommonSchemaDialog
to let them behave similar to MssqlDBCCDialog/AlertDialog and CommonSchemaTab. This means:
(1) A Messages tab will be added to MssqlShrinkDatabaseDialog to display warning messages.
(2) OK button will be disabled after warning messages are displayed in Messages tab.
(3) MssqlShrinkDatabaseDialog will remain open after warning messages are displayed, user needs to close it manually.
If you have different thoughts, please let me know.
@funfun: pls see this comment from Ivan: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/9543?tab=comment#89556DCF-7F18-97F5-E858-D3F3D1ACAE8B
This is irrelevant because SQL Server does not have problem to retrieve warning messages.
@funfun: pls see this comment from Ivan: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/9543?tab=comment#89556DCF-7F18-97F5-E858-D3F3D1ACAE8B
This is irrelevant because SQL Server does not have problem to retrieve warning messages.
17.0 - SVN r47215/17.0.0-rc-43
Fixed problem based on approach described here.
@Sachin,
Maybe we should change Cancel button's label from "Cancel" to "Close" after action is performed and OK button is disabled, see this screenshot. I will wait for your input before merge changes back to trunk.
[SP] Agreed - pls proceed
17.0 - SVN r47215/17.0.0-rc-43
Fixed problem based on approach described here.
@Sachin,
Maybe we should change Cancel button's label from "Cancel" to "Close" after action is performed and OK button is disabled, see this screenshot. I will wait for your input before merge changes back to trunk.
[SP] Agreed - pls proceed
17.0 - SVN r47230/17.0.0-rc-43
Changed Cancel button's label from Cancel to Close after shrink database action is successfully performed.
17.0 - SVN r47230/17.0.0-rc-43
Changed Cancel button's label from Cancel to Close after shrink database action is successfully performed.
18.0 - SVN r47242/18.0.0-dev-19
Merged changes made in 17.0 branch to trunk.
18.0 - SVN r47242/18.0.0-dev-19
Merged changes made in 17.0 branch to trunk.
Under Message Tab displayed changed database messages successfully. Refer updated screenshot 'Check_DBCC_RC-43.png'
Under Message Tab displayed changed database messages successfully. Refer updated screenshot 'Check_DBCC_RC-43.png'
Issue #13886 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build ADS 17.0.0-rc-43/18.0.0-dev-19 |
No time estimate |
2 issue links |
relates to #7059
Issue #7059Save and Close does not work for Alert |
relates to #12747
Issue #12747DBA-T - SQL Server - Storage Mngr : Toolbar options gives Warning:"CommonSchemaUtil.executeDDL() was not successful" |
@funfun: pls see this comment from Ivan: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/9543?tab=comment#89556DCF-7F18-97F5-E858-D3F3D1ACAE8B