Windows 10: SQL Server startup account permission

Infotech101 · Oct 2, 2021

How can I replace a process level tokenBypass traverse checkingAdjust memory quotas for a process

:)

Dyan Rey · Oct 2, 2021

SQL server 2014

Hello,

Incorrect user permissions is one of the possible reasons why you're having challenges in downloading SQL server 2014. We suggest that you check this
link. This page contains information on how to obtain the latest service pack for SQL
Server 2014.

Let us know how else we may help you.  

Brink · Oct 2, 2021

SQL Server + Python — What’s new

Python is one of the most popular and fastest-growing languages used today. Pyodbc (Python-SQL Server Connector) is an open source Python module maintained by Michael Kleehammer that uses ODBC Drivers to connect to SQL Server. It allows you to connect from the platform of your choice to SQL Server on-premises and in the cloud. Pyodbc is also cross platform and can be installed using pip.

We recently announced SQL Server v.Next CTP1 on Linux and Windows, which brings the power of SQL Server to both Windows and — for the first time ever — Linux. You can now connect your applications to SQL Server running on Linux, Windows and macOS (with Docker).

For our Python developers, we have a few updates that will improve Python connectivity with SQL Server. Pyodbc is now:

Officially supported: You can contact Microsoft Customer Service and Support (CSS) via phone, email, Twitter, forums, etc., to report and get help with any issue.

Available in Jupyter Notebooks for SQL Server: The Jupyter Notebook is a web application that allows you to create and share documents that contain live code, equations and visualizations.Pyodbc and its dependencies ship out of the box with Juypter notebooks on Azure. To get started, go to notebooks.azure.com and create a new Python 2 notebook or follow the instructions here. Check out the code sample and paste it in your notebook’s interactive prompt to get started.

Compatible with Python 3.5 and Django 1.10 through Django-pyodbc-azure.

Get started today

Try the new getting started tutorials that show you how to:

Install SQL Server on Linux or Windows or run on Docker in multiple platforms.

Create a simple app using C#, Java, Node.js, PHP and Python with SQL Server.

Create a simple app using popular web frameworks like Django with SQL Server.

Try out some cool SQL Server features that can make your apps shine.

Get the latest v17.0 RC1 versions of SQL Server Management Studio (SSMS) and SQL Server Data Tools (SSDT).

Get the mssql extension for Visual Studio Code and develop apps with SQL Server on Linux/macOS/Windows.

Connect with us

Join the conversation at https://gitter.im/mssqldev.

Sign up to stay informed about new SQL Server on Linux developments.

Learn more

Visit Connect(); to watch overview, security, high-availability and developer tools videos about SQL Server on Linux on demand.

Learn more

Go to the next release of SQL Server webpage to get started with interactive SQL Server on Linux hands-on labs for Linux administrators new to SQL Server and for existing SQL Server database administrators new to Linux.

Visit Connect(); to watch overview, security, high-availability and developer tools videos about SQL Server on Linux on demand.

Other videos in this series

Watch the to see how to get started with SQL Server on Linux in less than a minute.

SQL Server on Linux: use SQL Tools with SQL Server

SQL Server + Node.js: what’s new

SQL Server + Java: what’s new

SQL Server + C#: what’s new

SQL Server + PHP: what’s new

Click to expand...

Source: SQL Server + Python s new | SQL Server Blog

Brink · Oct 2, 2021

SQL Server Guidance against speculative execution vulnerabilities

SQL Server Guidance to protect against speculative execution side-channel vulnerabilities

Summary

Microsoft is aware of a new publicly disclosed class of vulnerabilities referred to as “speculative execution side-channel attacks” that affect many modern processors and operating systems including Intel, AMD, and ARM. Note: this issue will affect other systems such as Android, Chrome, iOS, MacOS, so we advise customers to seek out guidance from those vendors.

Microsoft has released several updates to help mitigate these vulnerabilities. We have also taken action to secure our cloud services. See the following sections for more details.

Microsoft has not received any information to indicate that these vulnerabilities have been used to attack customers at this time. Microsoft continues working closely with industry partners including chip makers, hardware OEMs, and app vendors to protect customers. To get all available protections, hardware/firmware and software updates are required. This includes microcode from device OEMs and in some cases updates to AV software as well.

More information about the vulnerabilities can be found here: Microsoft Security Advisory ADV180002.

Supported SQL Server versions impacted

The following versions are impacted when running on x86 and x64 processor systems: SQL Server 2008, SQL Server 2008R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017. IA64 (SQL Server 2008) is not believed to be impacted.

Recommendations

The following table outlines what customers should do, depending on the environment SQL Server is running in and what functionality is being used. Microsoft recommends customers deploy fixes using normal procedures to validate new binaries before deploying to production environments.

[table][tr][td]Scenario Number[/td] [td]Scenario Description[/td] [td]Priority Recommendation(s)[/td] [/tr] [tr][td]1[/td] [td]SQL Server is run on bare metal (no virtual machines) AND no other untrusted application logic (application tier) is run on the same machine AND no untrusted SQL Server extensibility interfaces are being used (see below for list)[/td] [td]No immediate need to patch. Please deploy updated OS and SQL patches after normal pre-production validation testing. Do not enable the registry settings in Windows to enable the microcode changes.[/td] [/tr] [tr][td]2[/td] [td]SQL Server is run in a virtual machine in a public hosting environment[/td] [td]For Azure: No VM image update necessary (see KB 4073235 for details). For other public hosts: refer to their guidance.[/td] [/tr] [tr][td]3[/td] [td]SQL Server is run in a virtual machine in a private hosting environment[/td] [td]Apply patch to Host OS or isolate SQL Server on dedicated physical hardware. Please refer to Windows OS guidance on whether microcode changes should be enabled.[/td] [/tr] [tr][td]4[/td] [td]SQL Server is run in a physical or virtual machine and is not isolated from other application logic running on the same machine or is using extensibility interfaces in SQL Server with untrusted code[/td] [td]

Apply OS patches as described in Scenario 3

Apply SQL Server patches, when available

If running with untrusted code on the same machine, please enable the microcode changes as described in the Windows OS guidance.

OR

Restrict use of extensibility interfaces to block untrusted code from executing on the machine (see below)

[/td] [/tr] [tr][td]5[/td] [td]Customers running SQL Server 2017 on Linux OSes (independent of whether extensibility interfaces are being used)[/td] [td]

Apply Linux OS patches

Apply Linux SQL Server patches

Consult with your Linux OS vendor about whether and how to enable the firmware changes

[/td] [/tr] [/table]

Performance Advisory:

Microsoft continues to do performance evaluation on the patched binaries. However, at the time of publication, Microsoft has not yet validated SQL Server performance with all microcode patches, nor has it validated performance in all Linux environments. Customers are advised to evaluate the performance of their specific application when applying patches. Please validate the performance impact of enabling microcode changes before deploying into a production environment. Microsoft will update this section with more information when it is available.

Available Builds:

At the time of publication, the following patched SQL Server builds are available for download:
Servicing Release

SQL Server 2017 CU3

SQL Server 2017 GDR

SQL Server 2016 SP1 CU7

SQL Server 2016 SP1 GDR

This document will be updated when additional patched builds are available.

For Windows OS Builds, please refer to the following guidance for the latest on available Windows builds:

Windows Guidance for Consumers

For Linux builds, please contact the Linux vendor to find the latest patched builds for your specific Linux distribution.

Untrusted SQL Server extensibility mechanisms

SQL CLR assemblies

R and Python packages running through the external scripts mechanism or run from the standalone R/Machine Learning studio on the same physical machine as SQL Server

SQL Agent extensibility points running on the same physical machine as SQL Server (ActiveX scripts)

Non-Microsoft OLE DB providers used in Linked Servers

Non-Microsoft Extended Stored Procedures

Mitigations to take if using untrusted code in SQL Server:

[table][tr][td]Scenario/Use Case[/td] [td]Mitigations/Suggested Steps[/td] [/tr] [tr][td]Running SQL Server with CLR enabled (sp_configure ‘clr enabled’, 1)[/td] [td]

If possible, disable CLR if it is not needed in your application to reduce the risk of any untrusted code being loaded into SQL Server

(SQL Server 2017+) If CLR is still needed in your application, enable only specific assemblies to be loaded using the “CLR Strict Security” feature (https://docs.microsoft.com/en-us/sql...trict-security) using sys.sp_add_trusted_assembly (https://docs.microsoft.com/en-us/sql...y-transact-sql)

Consider whether CLR code can be migrated to T-SQL equivalent code

Review security permissions to lock down scenarios where CLR-based operations can be used. Limit CREATE ASSEMBLY, EXTERNAL ACCESS ASSEMBLY, and UNSAFE ASSEMBLY permission to the minimum set of users/code paths to disallow loading new assemblies in an existing, deployed application

[/td] [/tr] [tr][td]Running R/Python external scripts from within SQL Server (sp_configure 'external scripts enabled', 1)[/td] [td]

If possible, disable the external scripts capability if not needed in your application to reduce attack surface area.

(SQL Server 2017+) If possible, migrate external scripts doing scoring to use the native scoring feature instead (https://docs.microsoft.com/en-us/sql...native-scoring)

Review security permissions to lock down scenarios where external scripts can be used. Limit EXECUTE ANY EXTERNAL SCRIPT permission to the minimum set of users/code paths to disallow arbitrary scripts from being executed

[/td] [/tr] [tr][td]Using Linked Servers (sp_addlinkedserver)[/td] [td]

Please review installed OLEDB providers and consider removing any untrusted OLEDB providers from the machine. (Please make sure that you do not remove OLEDB providers if they are used outside of SQL Server on the machine). An example on how to enumerate existing OLEDB providers is here: https://msdn.microsoft.com/en-us/lib...numerator.aspx

Please review and remove any unneeded linked servers from SQL Server (sp_dropserver) to reduce the possibility of any untrusted code being executed within the sqlservr.exe process

Review security permissions to lock down ALTER ANY LINKED SERVER permission to the minimum number of users.

Review Linked Server Login/Credential mappings (sp_addlinkedsvrlogin/sp_droplinkedsvrlogin) to limit who can execute operations over linked servers to the minimum set of users/scenarios.

[/td] [/tr] [tr][td]Using Extended Stored Procedures (sp_addextendedproc)[/td] [td]As Extended Stored Procedures are deprecated, please remove all uses of these and do not use them in production systems.[/td] [/tr] [/table]
Click to expand...

Source: https://support.microsoft.com/en-us/...for-sql-server

Windows 10: SQL Server startup account permission

SQL Server startup account permission

SQL Server startup account permission

SQL Server startup account permission

SQL Server startup account permission - Similar Threads - SQL Server startup

SQL server question

sql server

sql server

Sql server Reporting Server activation with Sql server Core edition

Sql server Reporting Server activation with Sql server Core edition

SQL server

SQL server

SQL server 2019

Microsoft SQL Server