This user account () has been banned from the forums
Viewing 10 posts - 1 through 11 (of 11 total)
This was removed by the editor as SPAM
February 8, 2026 at 7:41 pm
This was removed by the editor as SPAM
February 8, 2026 at 7:33 pm
This was removed by the editor as SPAM
February 8, 2026 at 7:26 pm
You cannot force a UK dd-mm-yyyy format in SQL if your reporting tool only accepts DATETIME. DATETIME itself has no format; it’s just a binary date-time value. The display format...
February 8, 2026 at 7:02 pm
Yes, this is a limitation of Azure Query Editor. It only returns the result of the final statement and can also hit a short execution timeout, so cursor output never...
January 31, 2026 at 7:34 pm
Correct.... Azure SQL Managed Instance automated backups cannot be restored using pure T-SQL or SQL Agent. They are only accessible through the Azure portal, PowerShell, Azure CLI, or REST API....
January 31, 2026 at 7:21 pm
You cannot restore Azure SQL Managed Instance automated backups using pure T-SQL or SQL Agent jobs. Those backups are not directly accessible. Restores must be triggered via the Azure portal,...
January 31, 2026 at 7:13 pm
You should use backup and restore for nightly sync. T-SQL alone can’t access Azure’s automated backups, so automate restores via T-SQL scripts, PowerShell, or Azure CLI.
January 30, 2026 at 8:10 pm
The trigger likely joins only on ParentId, causing old child records to be logged. Fix it by joining on both ParentId and ChildId and handling multiple rows correctly. Use Extended...
January 30, 2026 at 8:00 pm
Azure Query Editor only shows the last statement’s result and may timeout after 5 minutes. Cursors produce intermediate results that it does not display. Run cursors in SSMS or Azure...
January 30, 2026 at 7:53 pm
Viewing 10 posts - 1 through 11 (of 11 total)