Hi dataEnthusiast.  Yes, I can see the datasources and run reports without issue.  From everything I can see, the SSRS portal is behaving normally outside of the "Report Builder" button. ...

Hi Thom,

Thank you for the suggestion, I'll have to give that a shot!

Hi Jeff,

I was asked to pull this information because our cyber insurance company wants an approximation of the...

Hi Thom,

I guess it would depend on how close of an approximation it is.  I think 95% accurate approximation might be acceptable.

• This reply was modified 4 years, 2 months ago by  tarr94.

Thanks again Lowell.  I'll give those scripts a look!

Hi Lowell.  Thank you for the very helpful response (and for that Cost Threshhold for Parallelism query)!

I'd be curious to hear a bit more about your approach for choosing a...

Thank you both for your helpful responses!

Thanks for the responses, I'll take a look at both of these.  Sorry SGT, I never caught your last post on that thread, probably due to the gap in time,...

Thank you Federico and SGT for the responses.

Yeah, the ERP vendor does provide a solution that involves lots of Excel spreadsheets and macros, but the business is hoping to save...

Sue, thanks for the reply.  I'll take a look at that article.

Chris, thanks for the info.  Just to clarify, I'm fairly certain the log file always seems to grow when...

Thanks for the responses Sue and Leo.

At this point, my best guess is that the snapshot was impacted due to one of the developers on our team adding and later...

Thanks for the responses SQL_Hacker and Mike.  It sounds like transaction replication might be the way to go.

I'm surprised to learn that performance wouldn't be an issue.  As far as...

Thanks Karen.  Sounds like it is just an access or subscription related thing.  Just wanted to make sure I wasn't missing something obvious.

A good point on connection strings as well.

Thanks!

Thanks for the reply Lowell.

As far as workarounds go, I'm running into issues with using the data export wizard to populate the data on the other instance.  The error message...

It's a third party application, so unfortunately, we don't have control over the underlying T-SQL that's executing.  Is it a fair bet that if the transaction log is progressively growing...

A SQL Server update wiped the permissions from a different instance that also needed this permission set.  Once I put those back in place, this started working again.