Take a look here...

https://social.msdn.microsoft.com/Forums/security/en-US/edb5c2a4-ea69-4440-b2a2-0d1f156b8263/clr-types-for-sql-server-2016-install-error?forum=SQLServer2016Preview

And may I ask why you are using RC3 instead of RTM?

Thanks Zane - Steve Miron said that fixed the query!

Got the same results - but thanks...

This article explains how to resolve this issue permanently...

https://www.mssqltips.com/sqlservertip/3086/how-to-resolve-ssis-access-denied-error-in-sql-server-management-studio/

Try creating and using a date table...much simpler. This script will create an awesome one.

Full disclosure - I found this script here - I am not the author...

/****** Object:...

Like this? Your question is somewhat confusing and incomplete.

CASE

WHEN OOC_Code = '08' THEN SomeValue

WHEN OOC_Code = '0' THEN SomeValue

ELSE DefaultValue

END

You might try this first...

Open RegEdit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters

Create a New DWORD value with the name: SessTimeout set the value: 360 keep it Hexadecimal

https://support.microsoft.com/en-us/kb/102067

See if that works...

It might be helpful if you told us exactly what the monitoring software is. And are you using VM-Ware or Hyper-V for your virtualization?

I have had issues in the past when I used VARCHAR(MAX) as the data type for the body of an HTML email.

Try using NVARCHAR(MAX) instead...here is a little sample code...

Read this article...

http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/12/31/managing-tempdb-in-sql-server-tempdb-basics-version-store-simple-example.aspx

Memphis PASS Chapter? I'll be seeing you guys soon. Been working in Nashville until this June and have been meaning to attend...but I will be around in January...

No problem...

You need to use this install instead...

https://msdn.microsoft.com/en-us/mt429383

It is the 2016 Preview...it works fine for me.

Regards

No impersonation - the service account had 'Browser' permissions on the SSRS folders and it handled all the security access and report access via a custom web page and database....

I have worked with a system something like that before. We locked down the SSRS server by only allowing the service account that the security application ran under to...