September 12, 2018 at 12:03 am
I could not find any logical explanation about the following issue.
I connected SQL Azure Query Editor and I executed the transaction blog in two step.
First I executed BEGIN TRANSACTION blog and then I tried to run COMMIT blog
but the query editor returns very interesting error about this transaction blot.BEGIN TRANSACTION
UPDATE EditorSampleTable SET UserName='xxxxx'
WHERE ID=2
after this execution ı tried to run COMMIT BLOG in the same session
COMMIT TRAN
The error message is very interesting
Failed to execute query. Error: The COMMIT TRANSACTION request has no corresponding
BEGIN TRANSACTION.
And when ı tried to execute the same query Manegment Studio it executed proper.
September 12, 2018 at 5:32 am
So here's the deal, the Azure Query Editor window doesn't allow you to highlight a query and run it in parts. It runs the whole query as a single statement. I tested this several times. You can't do what you're trying to do there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 12, 2018 at 5:32 am
Wait though.... That doesn't make sense. Hang on. More testing needed.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 12, 2018 at 5:41 am
Sorry about that. I was able to replicate your problem. It looks like some sort of bug. From what I can tell (and I haven't tried setting up extended events to monitor this), the transaction without a commit or rollback is just rolled back. I can't see any evidence of any open or active transactions through the DMVs. I reported this as a bug. You should too. Click the little feedback icon and put in a frowny face (I guess we're all kids now).
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 12, 2018 at 6:10 am
Hi Grant;
Thanks for your reply.
Actually I thought that issue is a bug but
SQL Azure default isolation level confused me. Therefor
I posted a question.
September 12, 2018 at 6:17 am
Hi Grant;
Could you share your bug report link?
Thanks
September 12, 2018 at 6:26 am
ESAT ERKEC - Wednesday, September 12, 2018 6:17 AMHi Grant;
Could you share your bug report link?Thanks
I used the feedback link. There isn't a way to share it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply