sql-server-2016

I have a requirement to check records up to differing dates, depending on which day of the week it is currently. On a Friday I need for it to look at the entire next week, until Sunday after next. On any other day it should check the current week, up until the coming Sunday. I have the below currently but it's not working due to syntax error. Is it possible to do a CASE WHEN inside a WHERE clause? WHERE T0.[Status] IN ('R','P') AND CASE WHEN DATEPART(weekday,GETDATE()) = '5' THEN T0.[DueDate] >= GETDATE() AND <= DATEADD(day, 15 - DATEPART(weekday, GetDate()), GetDate()) WHEN DATEPART(weekday,

I used the official tutorial to create a default instance https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-ubuntu but now I want to create a named-instance and can't find how to do that SQL Server on Linux doesn't support the notion of "multi-instance", so there are no named instances on Linux. You can see that its Windows only feature here: https://docs.microsoft.com/en-us/sql/sql-server/install/work-with-multiple-versions-and-instances-of-sql-server?view=sql-server-2017 来源： https://stackoverflow.com/questions/41695344/how-can-i-create-named-instance-of-sql-server-on-ubuntu

It seems all I can find online are examples of table-valued parameters that require using a stored procedure. I recall doing this in the past without the stored procedure. Is that possible? This code keeps throwing an error about the type not being specified. SqlCommand cmd = new SqlCommand(@" UPDATE t1 SET t1.ScheduledStartUTC = t2.ScheduledStartUTC FROM ScheduleTickets AS t1 INNER JOIN @SetScheduledStart AS t2 ON t1.ScheduleId = t2.ScheduleId AND t1.PatchSessionId = t2.PatchSessionId ", c); cmd.Parameters.Add("@SetScheduledStart", SqlDbType.Structured).Value = SetScheduleTicketsDateDT; cmd

I am looking at creating temporal tables https://msdn.microsoft.com/en-us/library/mt604462.aspx in our database but I cant on a couple of tables that have computed columns. The error message returned is rather self explanatory "Computed column is defined with a user-defined function which is not allowed with system-versioned table" but I was hoping there was a way to exclude or ignore columns from being tracked? I have tried dropping the computed column creating the history table then adding the computed column back into the table but this didn't work. Any help is appreciated. Thanks Edit - I

We have a SQL Server 2016 database that employs Always Encrypted. Our recently published ASP.net web site attempts to pull data from this database, and when it does we get this error: Error: Failed to decrypt column 'EnSSd'. Failed to decrypt a column encryption key using key store provider: 'MSSQL_CERTIFICATE_STORE'. The last 10 bytes of the encrypted column encryption key are: 'B8-48-B3-62-90-0B-1D-A6-7D-80'. Certificate with thumbprint '97B0D3A64CADBE86FE23559AEE2783317655FD0F' not found in certificate store 'My' in certificate location 'CurrentUser'. Verify the certificate path in the

I use VS2015 with SQL Server Data Tools; I have some Reporting Services (RDL) reports. I want to deploy them to a Reporting Server with SQL Server 2014 installed. In my report project I set the TargetServerVersion to "SQL Server 2008R2, 2012 or 2014" , but the deploment process fails with an error similar to: Report Definition invalid, because namespace .../2016/... invalid. It is solved. You "MUST" recompile your report project and immediately afterwards you can deploy your reports without any problem. 来源： https://stackoverflow.com/questions/37816216/deploy-of-a-report-with-ssdt-2016

I am running Windows 10 Pro 64 bit on a dev box that has multiple monitors, 16 gigs DDR4 RAM, 4 Ghz I7, GTX 970. I run SQL Management Studio with SQL Server 2016 Developer Edition along with VS 2015 Enterprise Update 3. Yesterday I upgraded Sql Management Studio 2016 to 13.0.15700.28 and it was like a poison pill for my machine. Now after an hour or two it will throw an out of memory except: An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException' was thrown Now this is sometimes typical if you are doing very large return sets of over a few