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.Struggling with Rich Text Field
Hello Community, I have a SQL table which has a column containing rich text field tags. I am trying for 2 days now to get rid of the tags but nothing is working for me. <div class="ExternalClass00D082CB77D043AC975C783B3BC9B418">PR approval process complete, currently with procurement. EU to provide the Scope and SSJ. Else Procurement with reject the PR.</div> Below is how the text appears while in the actual website, the data appears like this: The removal process cannot be hard-coded because every record tags are different from another. For example see the below example: <div class="ExternalClass156752DF6D8A4BBF84D75235021E4A45">Demand status updated to Under Tech. Procurement - Pending PR Creation <div class="ExternalClass1A849FEC18A44CCE90E425ED0F54A1A2"><html> <p>One time Support Request.<br></p></html></div> </div> *I have attached the actual output of this from website If anyone can help me on how to clean the characters with a SQL function or maybe a C# code that will be very helpful. I have tried the below links and they do not solve my problem. https://www.codeproject.com/Tips/821281/Convert-RTF-to-Plain-Text-Revised-Again https://social.msdn.microsoft.com/Forums/en-US/143abeb5-f98a-4b47-a746-dd141bdd6df7/sql-query-to-retrieve-a-rich-text-memo-field?forum=sqlgetstarted Any help on this issue will be very much appreciated.Microsoft SQL Server 2017 Web Edition & Reporting Services 2017 Developer Edition error
Dear Community, I've setup a Microsoft SQL Server 2017 Web Edition and downloaded afterwards the Reporting Services 2017, because its no longer included in SQL Installation directly. During the setup of the Reporting Service 2017 Installation I had to choose the Edition and my choice was also there "Developer Edition". Now when I try to configure the Reporting Service I run into the following error message: "The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services." I added a print screen with the details. Does someone knows something about this error under Microsoft SQL Server 2017? Looking forward to every useful hint or input. Thanks and kind regards, Joël
