That's it. There was an issue with the line feed character which was causing the issue. I typed out the same code in a new window and everything...

When I run the following code (includes statement terminators) I get a different error message:

IF OBJECT_ID('usp_test','P') IS NULL

EXEC ('CREATE PROCEDURE usp_test AS select 1 as row1');

GO

ALTER PROCEDURE usp_test

AS

select 2 as...

If you drop and recreate then you lose all permissions settings. If you ALTER then the permissions are kept.

Interestingly enough, that query does work though.

This code works:

SELECT 1

GO

SELECT 1

GO

Yea, I checked that, and it's still set as GO

Here's the error message:

Msg 156, Level 15, State 1, Line 1

Incorrect syntax near the keyword 'ALTER'.

Msg 102, Level 15, State 1, Line 1

Incorrect syntax near 'GO'.

I use this syntax when...

The mcrn field is a grouping of multiple fields into one (not my design). The information stored in the error_check field is also included in the mcrn field. ...

Adding a clustered index fixed it. After adding the clustered index on those two columns the query returns in 0 seconds. Here are the new results from those...

Here are the results from the those two queries:

name rows ...

Thank you for the response! Unfortunately there can be 15+ specialties per client so showing the whole string of gauges as one horizontal row wouldn't look good either. ...

I was able to figure out a work around for this. While you can't filter a tablix based on row number you CAN set visibility based on it. ...

I've played around with it further and noticed that sometimes it goes through correctly but other times it doesn't. One specific time it fails is while writing WHEN clauses...