On the speaking/blogging side of things, I have a very badly maintained blog that has patches of 2-3 months of being regularly updated and then much longer periods of not...

You could split the database into several projects, and only deploy the ones you need. You can link the projects together using same database references.

So DBProjectA would contain the 2...

One benefit you get from using procs is you can restrict what the service account can see at a more granular level.

You can give the service account exec permissions on...

• This reply was modified 2 years, 5 months ago by  chris.johnson.0120.

Looking at this, the RequiredTable results are not possible from the query you've written. In the query, you select all of the columns from table 1, but the result rows...

I switched jobs late last year, almost entirely because of the attitude towards the development team embedded in the culture at my previous job. I was one of the last...

• This reply was modified 2 years, 9 months ago by  chris.johnson.0120.

I gave my first ever conference talk at New Stars of Data. That's a pretty huge win for me, and helps to balance out that I didn't manage to do...

Just FYI, the reason you're getting NULLs in the code you have is the PARSENAME function.

This function is designed to return a part of an object name. As objects can...

I'm by no means an API expert, but you want some code that will call the API in a similar way to Postman. This might be a bit of C#...

Option 2 is probably the way to go. Cross database dependencies are very difficult to deal with in SSDT. I always found I had to do a certain amount...

+1 on driving ETL pipelines through metadata where possible. I've implemented systems like that in a few places, and it can be more of an upfront cost but it makes...

I usually have a lot of long weekends away doing things that tend to eat up my yearly holiday. With most of those looking like they won't happen, I've booked...

I've had a couple of cases where I've wanted to share a sequence across two or more tables. Usually when I have several different sources for something like customer data,...

It sounds to me like you actually want to normalise your data a bit.

So, split TableA into Transaction and Item, where Transaction holds TransactionNo, TransactionDate, and Item holds ItemNo and...

Maybe LocationAddress if you're primarily looking at attributes of an address?

There are a few ways to approach this. I'd usually use a correlated sub-query as below:

SELECT
  PremChar.PREM_ID AS PremiseID
, MAX(CASE -- The MAX will ignore NULLs...