Skip to content

Commit 7a8253a

Browse files
v-aljev-alje
committed
Bringing even with master.
2 parents c8d63e1 + 7086b07 commit 7a8253a

File tree

3 files changed

+162
-2
lines changed

3 files changed

+162
-2
lines changed

‎docs/sql-server/sql-server-privacy.md

Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,158 @@
1+
---
2+
title: "SQL Server Privacy Supplement | Microsoft Docs"
3+
ms.date: "2/19/2018"
4+
ms.prod: "sql-non-specified"
5+
ms.prod_service: "sql-non-specified"
6+
ms.service: ""
7+
ms.component: "sql-non-specified"
8+
ms.reviewer: ""
9+
ms.suite: "sql"
10+
ms.custom: ""
11+
ms.technology: ""
12+
ms.tgt_pltfrm: ""
13+
ms.topic: "article"
14+
f1_keywords:
15+
helpviewer_keywords:
16+
author: "craigg-msft"
17+
ms.author: "craigg"
18+
manager: "jhubbard"
19+
ms.workload: "Active"
20+
---
21+
# SQL Server Privacy Supplement
22+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
23+
24+
This article summarizes the behavior of different data objects used within SQL Server and how the objects are used to pass information of a personal or confidential manner. The data classification in this article only applies to versions of the SQL Server on-premises product. It does not apply to the items:
25+
26+
- Azure SQL Database
27+
- SQL Server Management Studio (SSMS)
28+
- SQL Server Data Tools (SSDT)
29+
- SQL Operations Studio
30+
31+
Definition of *Permitted usage Scenarios*. For the context of this article, Microsoft defines “Permitted Usages Scenarios” as actions or activities that are initiated by Microsoft.
32+
33+
***
34+
35+
>## Access Control
36+
37+
Credential-related information used to secure logins, users, or accounts within a SQL Server installation.
38+
39+
### Examples of access control
40+
41+
- Passwords
42+
- Certificates
43+
44+
### Permitted Usage Scenarios
45+
46+
|Scenario |Access Restrictions |Retention Requirements |
47+
|---------|---------|---------|
48+
|These credentials never leave the user machine via Usage Feedback. |- |- |
49+
|Crash Dumps may contain Access Control Data. |- |Crash Dumps: Maximum 30 days. |
50+
|These credentials never leave the user machine via User Feedback unless Customer injects it manually |Limit to Microsoft internal use with no third-party access. |User Feedback: Max 1 year |
51+
|
52+
>## Customer Content
53+
54+
Customer content is defined as data stored within user tables, directly or indirectly. The data includes statistics or user literals within query texts that might be stored within user tables.
55+
56+
### Examples of customer content
57+
58+
- Data values stored within the rows of any user table.
59+
- Statistics objects containing copies of values within the rows of any user table.
60+
- Query texts containing literal values.
61+
62+
### Permitted Usage Scenarios
63+
|Scenario |Access Restrictions |Retention Requirements |
64+
|---------|---------|---------|
65+
|This data does not leave the user machine via Usage Feedback. |- |- |
66+
|Crash Dumps may contain Customer Content and be emitted to Microsoft. |- |Crash Dumps: Max 30 days. |
67+
|Customers with their consent can send User Feedback that contains Customer Content to Microsoft. |Limit to Microsoft internal with no third-party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
68+
69+
>## End-User Identifiable Information (EUII)
70+
71+
Data received from a user, or generated from their use of the product.
72+
- Linkable to an individual user.
73+
- Does not contain content.
74+
75+
### Examples end-User identifiable information
76+
77+
- Interface Identification. The Full IP address
78+
- Machine Name
79+
- Login/User names
80+
- Local-part of e-mail address ([email protected])
81+
- Location Information
82+
- Customer Identification
83+
84+
### Permitted Usage Scenarios
85+
86+
|Scenario |Access Restrictions |Retention Requirements|
87+
|---------|---------|---------|
88+
|This data does not leave the user machine via Usage Feedback. |- |- |
89+
|Crash Dumps may contain EUII and be emitted to Microsoft. |- |Crash Dumps: Max 30 days |
90+
|Customer Identification ID may be emitted to Microsoft to deliver new hybrid and cloud features that the users have subscribed to. |- |Currently no such hybrid or cloud features exist.|
91+
|Customers with their consent can send User Feedback that contains Customer Content to Microsoft.|Limit to Microsoft internal use with no third-party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
92+
93+
>## Internet-Based Services Data
94+
95+
Data needed to provide Internet-based services, per the SQL Server EULA.
96+
97+
### Examples of Internet-based services data
98+
99+
- Computer Specification Information
100+
- Browser name/version
101+
- SQL Server version
102+
- Language Code
103+
- An IP Address with specific octets removed
104+
- Map Data
105+
106+
### Permitted Usage Scenarios
107+
108+
|Scenario |Access Restrictions |Retention Requirements|
109+
|---------|---------|---------|
110+
|May be used by Microsoft to improve features and/or fix bugs in current features. |Limit to Microsoft internal use with no third-party access. Microsoft can expose the data to the original customer. For example, dashboards |Min 90 days - Max 3 years |
111+
|Customers with their consent can send User Feedback that contains Customer Content to Microsoft. |Limit to Microsoft internal use with no third-party access. |Customers with their consent can send User Feedback that contains Customer Content to Microsoft. |
112+
|Power View and SQL Reporting Services Map Item(s) may send data for use of Bing Maps. |Limit to session data |- |
113+
114+
>## System Metadata
115+
116+
Data generated in the course of running the server. The data does not contain Customer content.
117+
118+
### Examples of system metadata
119+
120+
The following are considered system metadata when they do not inlcude customer content, customer access control, or EUII:
121+
122+
- Database GUID
123+
- Hash of Machine Name
124+
- Hash of Instance Name
125+
- Hash of Application Name
126+
- Behavioral/Usage Data
127+
- SQL Customer Experience improvement program data (SQLCEIP)
128+
- Server configuration data, for example settings of sp_configure
129+
- Feature configuration data
130+
- Event Names and Error Codes
131+
132+
### Permitted Usage Scenarios
133+
134+
|Scenario |Access Restrictions |Retention Requirements|
135+
|---------|---------|---------|
136+
|May be used by Microsoft to improve features and or fix bugs in current features.|Limit to Microsoft internal use with no third-party access. |Min 90 days - Max 3 years |
137+
|May be used to make suggestions to the customer. For example, “Based on your usage of the product, consider using feature X since it would perform better.” |Microsoft can expose the data to the original customer, for example through dashboards. |Customer Data Security Logs: Min 3 years - Max 6 years |
138+
May be used by Microsoft for future product planning. |Microsoft may share this information with other hardware and software vendors to improve how their products run with Microsoft software. |Min 90 days - Max 3 years|
139+
|May be used by Microsoft to provide cloud-based services based on emitted Usage Feedback. For example, a customer dashboard showing feature usage across all SQL Server installations in an organization. |Microsoft can expose the data to the original customer, for example, through dashboards. |Min 90 days - Max 3 years |
140+
|Customers with their consent can send User Feedback that contains Customer Content to Microsoft. |Limit to Microsoft internal with no third-party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
141+
142+
>## Object Metadata
143+
144+
Data that describes or is used to configure servers, databases, tables, and other resources. Object metadata includes database table and column names but not the contents of database rows or other Customer Content. Customers should not place personal data, such as end-user identifiable information in Object Metadata fields or create applications designed to store personal data in these fields.
145+
146+
### Examples of object metadata
147+
148+
- SQL Server database names
149+
- Table names and Column names
150+
- Statistics Names
151+
152+
### Permitted Usage Scenarios
153+
154+
|Scenario |Access Restrictions |Retention Requirements|
155+
|---------|---------|---------|
156+
|May be used by Microsoft to improve features and or fix bugs in current features. |Limited to Microsoft internal use with no third-party access. |Min 90 days - Max 3 years|
157+
158+
[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]

‎docs/ssms/download-sql-server-management-studio-ssms.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,7 @@ Showplan:
108108
* This version of SSMS works with all [supported versions of SQL Server 2008 - SQL Server 2017](https://support.microsoft.com/lifecycle?C2=1044) and provides the greatest level of support for working with the latest cloud features in Azure SQL Database and Azure SQL Data Warehouse.
109109
* There is no explicit block for SQL Server 2000 or SQL Server 2005, but some features may not work properly.
110110
* Additionally, SSMS 17.x can be installed side by side with SSMS 16.x or SQL Server 2014 SSMS and earlier.
111+
* SQL Server Integration Services (SSIS) - SSMS version 17.x does not support connecting to the legacy SQL Server Integration Services service. To connect to an earlier version of the legacy Integration Services, use the version of SSMS aligned with the version of SQL Server. For example, use SSMS 16.x to connect to the legacy SQL Server 2016 Integration Services service. SSMS 17.x and SSMS 16.x can be installed side-by-side on the same computer. Since the release of SQL Server 2012, the SSIS Catalog database, SSISDB, is the recommended way to store, manage, run, and monitor Integration Services packages.
111112

112113
## Supported Operating systems
113114

@@ -143,6 +144,7 @@ Data classification:
143144
- Removing a classification and then manually adding a new classification for the same column results in the old information type and sensitivity label being assigned to the column in the main view.<br>
144145
*Workaround*: Assign the new information type and sensitivity label after the classification was added back to the main view and before saving.
145146

147+
146148
## Previous releases
147149

148150
[Previous SQL Server Management Studio Releases](../ssms/sql-server-management-studio-changelog-ssms.md#previous-ssms-releases)

‎docs/t-sql/database-console-commands/dbcc-dropcleanbuffers-transact-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,10 +57,10 @@ DBCC DROPCLEANBUFFERS ( COMPUTE | ALL ) [ WITH NO_INFOMSGS ]
5757
Suppresses all informational messages. Informational messages are always suppressed on [!INCLUDE[ssSDW](../../includes/sssdw-md.md)] and [!INCLUDE[ssPDW](../../includes/sspdw-md.md)].
5858

5959
COMPUTE
60-
Purge the query plan cache from each Compute node.
60+
Purge the data cache in memory from each Compute node.
6161

6262
ALL
63-
Purge the query plan cache from each Compute node and from the Control node. This is the default if you do not specify a value.
63+
Purge the data cache in memory from each Compute node and from the Control node. This is the default if you do not specify a value.
6464

6565
## Remarks
6666
Use DBCC DROPCLEANBUFFERS to test queries with a cold buffer cache without shutting down and restarting the server.

0 commit comments

Comments
 (0)