Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with sql-server-2019
Search options not deleted
user 224761
SQL Server 2019 (major build version 15.00.xxxx). Please also tag sql-server.
0
votes
1
answer
99
views
Does the length of the fields play a role in index access in MS-SQL?
Last week I had already started two threads dealing with slow SQL selects that probably did not use the index.
Today I noticed the following: The customer and the material are involved in almost all i …
- 69
0
votes
2
answers
1k
views
A slow query on MS-SQL-Server 2019 cannot be optimized
In the following thread I received some important and valuable information on how I can improve a slow query on MS-SQL-Server 2019.
However, that didn't do very much.
First I deleted all non-clustered …
- 69
3
votes
3
answers
136
views
How do I determine the correct index on MS-SQL-Server based on a select?
I have two questions about the index management of MS-SQL-Server 2019
If the term "table scan" appears in the execution plan, is that an indication of a "full table scan", and that means that no inde …
- 69
3
votes
6
answers
10k
views
MS-SQL-Server 2019 is slower than SQL-Server 2008
Since we updated from SQL Server 2008 to 2019, the queries have become much slower.
The following query ran for ten minutes on version 2008. On version 2019 it runs for over 30 minutes.
Until yesterda …
- 69