On a Windows 2008 R2 server running SQL Server 2012, I started getting these recently:

SQL Server Scheduled Job 'Intraday Backup 1500.Subplan_1' (0x65C01B2C6FA5124493CA18E3665B09AA) - Status: Failed - Invoked on: 2012-09-10 16:18:58 - Message: The job failed.  Unable to determine if the owner (<DOMAIN>\administrator) of job Intraday Backup 1500.Subplan_1 has server access (reason: Could not obtain information about Windows NT group/user '<DOMAIN>\administrator', error code 0x6e. [SQLSTATE 42000] (Error 15404)).

After some research it seemed that I should change the owner of the job to something else, so I made it SQLServerAgent, that seemed to be the only thing that worked.

Now I'm getting these:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{FDC3723D-1588-4BA3-92D4-42C430735D7D}
 and APPID 
{83B33982-693D-4824-B42E-7196AE61BB05}
 to the user NT SERVICE\SQLSERVERAGENT SID (S-1-5-80-355555556-2666666661-2777777773-2888888883-1999999990) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

I did my usual digging around and couldn't find much that was useful, apart from notes about locating the appid mentioned in the registry and going to Component Services to fix the permissions.  The appid translates to MS DTS Server, nothing like that is listed in DCOM.



I've done a fair bit of searching and reading and got nowhere with this, maybe I'm missing the point.  The job does run now, I'm just averse to errors in the Event Log, I mean they wouldn't be there if it didn't matter, would they?

May I know if SQL Server polybase 2019 (or before) support what kind of data format ?

Json ? xml ? picture ? audio ?

I know that SQL Server 2019 can run python external script , can these python external script access data out of SQL Server (also polybase) , and import it to sql server ?

Any difference between polybase in SQL Server Windows Version and in big data cluster version ?

What's the actual difference of data pool and storage pool in BDC arch .?

Data pool

The data pool is used for data persistence and caching. The data pool consists of one or more pods running SQL Server on Linux. It is used to ingest data from SQL queries or Spark jobs. SQL Server big data cluster data marts are persisted in the data pool.

Storage pool

The storage pool consists of storage pool pods comprised of SQL Server on Linux, Spark, and HDFS. All the storage nodes in a SQL Server big data cluster are members of an HDFS cluster.

https://docs.microsoft.com/en-us/sql/big-data-cluster/big-data-cluster-overview?view=sql-server-ver15

Hi,

My database mail was working fine. Recently i have noticed that my database mail is not working.

Please help

Thank You,

Zahid

Security / System Center Configuration Manager Current Branch / SQL

Hello,

I'm using SSMS v18.3  and I do not see any Debugging option.

I have a query and I want to step through each line as it executes.

Please help.

Hi All,

I am getting the above error msg when querying data from SQL 2014 SP1 to SQL 2014 SP1.

The issue is only with few tables and when we fetch the same data through a Stored procedure it works fine, Hence the issue is only when we fetch the data as an adhoc query

for eg: select * from [link_name].dbname.dbo.select * from ABC (Gives the error)

for eg: EXEC [link_name].dbname.dbo.USP_SELECT_ABC(works fine)

code of USP_SELECT_ABC

create proc USP_SELECT_ABC

as

select * from ABC

Hope  the above scenario is clear to you all

aa

Hi,

I have the new 3 node FCI SQL Server Cluster (SQL Server Enterprise 2019 on Win Server 2019). The first and second node are also the primary replica in the always on topology. Filestream were configured (level 3 remote client access) during installation without any problems. After we restored filestream database, we get error in the application (after call stored procedure for get PathName() and Get_filestream_transaction_context(). The procedure return PathName value.

======================================================

The device is not ready
=======================================================
Iznimka = System.ComponentModel.Win32Exception (0x80004005): The device is not ready
   at System.Data.SqlTypes.SqlFileStream.OpenSqlFileStream(String path, Byte[] transactionContext, FileAccess access, FileOptions options, Int64 allocationSize)
   at System.Data.SqlTypes.SqlFileStream..ctor(String path, Byte[] transactionContext, FileAccess access, FileOptions options, Int64 allocationSize)

The configuration manager values on FILESTREAM tab is all enabled, only the last one "Enable remote client access to Filestream data" is grey out but checked.

I have try to disable and then again enable the filestream in the configuration manager , and after enabling I got error

"The specified Filestream share name"  does not match the file share resource on the current failover cluster. Change the FIlestream share name to match (0x800713b8)"

In the registry is stored value correct value  for the share.

I can manual change the registry and then the filestream is enabled but is not working, we have same error.

In Failover manager when we want to check the properties of the file share, we get error "unable to load information for the share" and also in the SSMS, Server properties Share name is blank.

I have installed CU5 for SQL server 2019, and run repair installation of the SQL Server. In SQL log we do not have any errors.

Please help, is it  bug or something,I'm out of any idea regarding this problem.

Kind Regards

I have a problem with a simple query that takes more than 30 second to complete. The query is a simple "SELECT" from a single table and the resultset contains 64 rows.
Im not sure why it takes so long because the query is simple and the execution plan dont show any issues.

I checked the Sql Server log and found this message multiple times:
"A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1142644, committed (KB): 2241136, memory utilization: 50%".
So i checked the memory usage of the Sql Server process while the query is running and it increases from ~400MB to ~1.5GB. It seems that the OS started paging and slows down everything.
But why?

I have to mention that the varchar columns of the table uses the collation Latin1_General_100_CI_AI_SC_UTF8. When i switch the collation to Latin1_General_100_CI_AI_SC it runs without  any problems.

Is this a encoding bug in the SQL Server 2019? Can anyone else reproduce this or can explain me what is going on?

What i used:

• SQL Server 2019, SELECT @@Version:  Microsoft SQL Server 2019 (RTM-CU5) (KB4552255) - 15.0.4043.16 (X64)   Jun 10 2020 18:25:25   Copyright (C) 2019 Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
• ODBC Driver 64-bit, 2017.175.02.01
• Microsoft SQL Management Studio v18.5, 15.0.18330.0

The query

SELECT
[ID] AS [ID]
,[Column1]
,[Column2]
,[Column3]
,[Column4]
,[Column5]
,[Column6]
,[Column7]
,[Column8]
FROM [dbo].[MyTable]
WHERE [ID] IN (3,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81)

The table

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[MyTable](
	[ID] [int] NOT NULL,
	[Column1] [varchar](250) COLLATE Latin1_General_100_CI_AI_SC_UTF8 NULL,
	[Column2] [varchar](36) COLLATE Latin1_General_100_CI_AI_SC_UTF8 NULL,
	[Column3] [int] NULL,
	[Column4] [int] NULL,
	[Column5] [int] NULL,
	[Column6] [varchar](250) COLLATE Latin1_General_100_CI_AI_SC_UTF8 NULL,
	[Column7] [varchar](250) COLLATE Latin1_General_100_CI_AI_SC_UTF8 NULL,
	[Column8] [int] NULL,
 CONSTRAINT [PK_MyTable] PRIMARY KEY CLUSTERED 
(
	[ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO

The data

INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (3, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (7, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (8, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (9, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (11, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (12, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (13, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (14, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (15, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (16, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (17, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (18, N'ABC', N'abc', 1227, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (19, N'ABC', N'abc', 1227, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (20, N'ABC', N'abc', 1227, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (21, N'ABC', N'abc', 1227, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (22, N'ABC', N'abc', 1229, 6142, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (23, N'ABC', N'abc', 1257, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (24, N'ABC', N'abc', 1257, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (25, N'ABC', N'abc', 1257, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (26, N'ABC', N'abc', 1257, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (27, N'ABC', N'abc', 1230, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (28, N'ABC', N'abc', 1230, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (29, N'ABC', N'abc', 1230, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (30, N'ABC', N'abc', 1230, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (31, N'ABC', N'abc', 1231, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (32, N'ABC', N'abc', 1231, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (33, N'ABC', N'abc', 1231, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (34, N'ABC', N'abc', 1231, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (35, N'ABC', N'abc', 1233, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (36, N'ABC', N'abc', 1233, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (37, N'ABC', N'abc', 1233, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (38, N'ABC', N'abc', 1233, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (39, N'ABC', N'abc', 1232, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (40, N'ABC', N'abc', 1232, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (41, N'ABC', N'abc', 1232, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (42, N'ABC', N'abc', 1232, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (43, N'ABC', N'abc', 1228, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (44, N'ABC', N'abc', 1228, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (45, N'ABC', N'abc', 1228, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (46, N'ABC', N'abc', 1228, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (47, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (48, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (49, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (50, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (51, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (52, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (53, N'ABC', N'abc', 1227, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (64, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (65, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (66, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (67, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (68, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (69, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (70, N'ABC', N'abc', 1257, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (71, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (72, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (73, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (74, N'ABC', N'abc', 1226, 6605, 1, N'abc', NULL, 1)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (75, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (76, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (77, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (78, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (79, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (80, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)
INSERT [dbo].[MyTable] ([ID], [Column1], [Column2], [Column3], [Column4], [Column5], [Column6], [Column7], [Column8]) VALUES (81, N'ABC', N'abc', 1226, 6103, 1, N'abc', NULL, 4)

Hello,

I'm not very good with scripting loops.

I want to loop through each database and check the LogFile Size and Free Space on Log File.

If it meets these conditions I want to truncate.

If @logsize >= 20000 -- and @logspace >= 80  
set @SQL = 'use'  + [Database_Name]  +  'dbcc shrinkfile ([LogFileName], 20000, TRUNCATEONLY) WITH NO_INFOMSGS'
exec (@SQL)

Please help

Hello all,

Do you know when is the release date of the SQL Server 2020 (Also named SQL2020 and SQL Server 16.0 (?))?

We need to work on the planning for verification testing with SQL2020.

Thank you!

- Trang

Hi all,

I am using sql server 2017, and I was trying to optimize a query that runs slowly. Surfing some blogs, I came across query hints and used this one:

option(use hint('DISABLE_OPTIMIZED_NESTED_LOOP'), maxdop 1);

Unfortunately, what happened is now the query runs even slower, and I couldn't figure out how to reverse the effect of this hint.

My questions would be:

1- Does this hint affect other users and their queries too ?? 

2- How to restore the query optimizer to its default settings ??

I appreciate you help in this matter.

Best Regards

Greetings. I recently moved a DB that holds DBA service account passwords from a 2012 instance to 2019. The passwords are encrypted using column level encryption. When I run a sproc to decrypt the password and return the unencrypted value all is well. However,  when I insert new data into the table the password into the table it gets stored as a NULL value. 

Google tells me the two main reasons for this are 1) The symmetric key is not open. We're running a sproc that handles this, and that didn't change between versions. 2) ansi_padding being off. As such I did a "set ansi_padding on alter table foo alter column foo" and that didn't fix it either. 

I should note that the migration itself wasn't the smoothest, and those woes can be found here. However, I have the luxury of simply "rebuilding" this encryption column if needed. The table is tiny and I'm the only FTE that uses it, all I care about is resolving the issue. 

Ideas?

Thanks in advance! ChrisRDBA

https://docs.microsoft.com/en-us/sql/relational-databases/polybase/configure-scale-out-groups-windows?view=sql-server-ver15

when I come accross the above DOC, and just wondering if the scale out ability can be benefit/enabled for all the external data source destination ? Here mention HDFS/Blob.  what about Oracle/SQLServer/ODBC.......

May I know if the following 

Queries with forced plans ,queries with high variance are available on SQL Server 2016, however require much update SSMS to view ?

And the Query wait stats are from SQL Server 2017 ?

I have a postgres db and would like to convert to SQL Express or standard edition.  Is there a conversion or migration tool available?

I can dump the postgres db to a sql file but MS has slightly different syntax and datatypes so I have to go in a manually modify the sql file for every table and data type.  Is there an easier way?  Thanks!

What actual objects are persisted under the hidden database "resourcedb"

What's the difference between the following ?