Browser for SQL Server 2017 and 2019
Hello, my question is the following. Despite having the latest updates released for SQL Server 2019 and 2017, I notice that SQL Server Browser does not change versions, remaining in the versions mentioned below. I would like to know if they are in fact the latest versions of SQL Server Browser released in the 2017 and 2019 packages. If the versions below are correct, if they really have not been updated. Browser for SQL Server 2017 14.0.1000.169 Browser for SQL Server 2019 15.0.2000.5
SQL Server audit logs incorrect info on column object_name
Hi, during an audit check on database events, i have noticed that sometimes on DDL events, when temp tables are mentioned, sql server 2017 logs incorrect information on columns schema_name and object_name and the statement column proves this: Moreover, on the two columns the info for the object on which the DDL was applied, is taken randomly, it may show the first table, or the second, making this difficult to prove the actions in case of audits: Sadly, i haven't found this reported anywhere..
Moving SQL Server 2017 from GDR Path to CU Path
Hello everyone, I have been scouring the internet and am not able to find the answer I need so I turn to you for assistance. Here is the situation, we have an AG set up on SQL Server 2017. Currently both of those servers are on patch 14.0.2052.1 or 5029375 Security update for SQL Server 2017 GDR: October 10, 2023. I would like to change us to be on at least CU 15 (yes I know CU 31 is the latest but the issue requiring this change is CU 15), but there is nothing I can find about how to change from the GDR Path to the CU Path. The only option I can see is to roll EVERYTHING back to the 2017 RTM, then apply CU 31. That isn't a great option as this is a 24/7 application. So, how in the world do you change from GDR to CU? Thanks in advance, ChapUsing SQL Service Broker for asynchronous external script (R / Python) execution in OLTP systems
First published on MSDN on Oct 19, 2017 Authored by Arvind Shyamsundar (Microsoft)Credits: Prasad Wagle, Srinivasa Babu Valluri, Arun Jayapal, Ranga Bondada, Anand Joseph (members of the Sayint by Zen3 team)Reviewers: Nellie Gustafsson, Umachandar Jayachandran, Dimitri Furman (Microsoft)This blog post was inspired our recent work with the Sayint dev team, who are a part of Zen3 Infosolutions.Performance impact of memory grants on data loads into Columnstore tables
First published on MSDN on Jun 02, 2017 Reviewed by: Dimitri Furman, Sanjay Mishra, Mike Weiner, Arvind Shyamsundar, Kun Cheng, Suresh Kandoth, John HoangBackgroundSome of the best practices when bulk inserting into a clustered Columnstore table are: Specifying a batch size close to 1048576 rows, or at least greater than 102400 rows, so that they land into compressed row groups directly.Build a recommendation system with the support for graph data in SQL Server 2017 and Azure SQL DB
First published on MSDN on Apr 21, 2017 Authored by Arvind Shyamsundar and Shreya Verma Reviewed by Dimitri Furman, Joe Sack, Sanjay Mishra, Denzil Ribeiro, Mike Weiner, Rajesh SetlemGraphs are a very common way to represent networks and relationships between objects.
SQL server 2017 Replication issue on specific tables and view
Hi, We got below error in our prod environment when added 2 more tables and 1 view to replicate to another server in existing replication setup. We tested out that scenario in our staging and dev environment and no issue occurred. We are not sure it's happened because of object schema or data issue. Please help advise how we can overcome below issue. 2021-11-13 10:46:30.094 Connecting to Subscriber 'ServerName' 2021-11-13 10:46:30.125 Initializing 2021-11-13 10:47:27.766 Skipping file 'ORC_MTL_ONHAND9ce349e7_148.pre' because it has already been delivered for a previous article or by a previously interrupted snapshot. 2021-11-13 10:47:27.766 Skipping file 'ORC_MTL_ONHANDa7c3e34f_116.pre' because it has already been delivered for a previous article or by a previously interrupted snapshot. 2021-11-13 10:47:27.781 Skipping file 'ORC_MTL_ONHANDc7c3e34f_115.pre' because it has already been delivered for a previous article or by a previously interrupted snapshot. 2021-11-13 10:47:27.828 Agent message code 1934. INSERT failed because the following SET options have incorrect settings: 'ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. 2021-11-13 10:47:27.860 Category:COMMAND Source: Failed Command Number: Message: create procedure [sp_MSins_dboORC_MTL_ONHAND_QUANTITIES_1] @c1 numeric(15,0), @c2 int, @c3 int, @c4 datetime2, @c5 datetime2, @c6 int, @c7 datetime2, @c8 int, @c9 numeric(38,0), @c10 nvarchar(10), @c11 int, @c12 int, @c13 int, @c14 datetime2, @c15 int, @c16 numeric(38,0), @c17 numeric(38,0) as begin insert into [dbo].[ORC_MTL_ONHAND_QUANTITIES_1] ( [MTL_ONHAND_QUANTITIES_KEY], [INVENTORY_ITEM_ID], [ORGANIZATI 2021-11-13 10:47:27.860 Category:NULL Source: Microsoft SQL Server Native Client 11.0 Number: 1934 Message: INSERT failed because the following SET options have incorrect settings: 'ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. Thanks & Best Regards, Theingi
