The Heap™ – Consultancy ©®

HOWEVER, lack of industry pressure (there's only 3 players in the UK for this field) means we're completely stagnant in terms of technical process etc

The company tends to just throw money at issues rather than doing things the best way

so double edged sword

Peter Vandivier

10:49 AM

a double edged sword made of money

George.Palacios

cash shank

Peter Vandivier

💵🔥💵🔥💵🔥💵🔥

George.Palacios

We're also not VAT registered

which is kinda funny

We're a mutual - not for profit

Peter Vandivier

so... the compliance training for my company has been translated from japanese pretty casually

coming next is the "Harassment (Power Sex)" portion of the training

well mark me down as scared and horny meme

►

George.Palacios

11:04 AM

LOL

7 hours later…

billinkc

5:47 PM

seeekrit hat, engaged

Tom V - Team Monica

6:02 PM

@billinkc you're so welcoming

billinkc

All the more so with the hat in place

ErikE

6:30 PM

Folks, could you recommend your favorite way in a change script consisting of multiple batches to avoid running subsequent batches after a failed batch? I found dba.stackexchange.com/questions/194515/… but wondered if it got enough attention or might be missing some cool tips.

At first I was thinking SET XACT_ABORT ON was good, but then wondered about instead just tracking whether an error occurred, then at the end I can rollback the whole transaction? Only... tracking an error seems kind of hard. I could start two transactions, then rollback one on error, but keep the second, and use tran count to track which state we're in? That seems hacky. Any thoughts?

billinkc

The Redgate change scripts use transactions + error checking and a goto after each change to jump to the end of the script. Not saying that's good or bad, just an approach a large commercial vendor takes

Andriy M

7:11 PM

Depending on what the scripts are doing, playing with SET NOEXEC ON/OFF could be an option too.

GOTO won't work if you need to skip multiple batches. You can only jump to a point within the same batch.

billinkc

7:22 PM

Batches? We don't need no stinking batches. I don't have to show you no stinking batches

Cade Roux

7:53 PM

I'm trying to move from Profiler to Extended Events to look at performance of SSRS reports. I picked sql_statement_starting and sql_statement_completed and I put a filter to exclude the ReportServer database. But all I see in Extended events is a bunch of stuff like this in the database I am interested in:

SELECT DATABASEPROPERTYEX(DB_NAME(), 'Collation'), COLLATIONPROPERTY(CONVERT(char, DATABASEPROPERTYEX(DB_NAME(), 'collation')), 'LCID')

No matter what report I am running.

Cade Roux

8:11 PM

Looks like reports get converted to temporary stored procedures - I do see some activity in sp_statement of queries from the report.

2 hours later…