Information Systems software coding for a proprietry Learning Management System (LMS) with complete integration and stringent Active Directory hybrid CISCO Systems/IEEE port map stack to route The University of Western Australia and Harvard University from a hardware SQL Server with RAID-configured Virtual SQL Servers in the cloud-hybrid Multipoint-protocol virtualisation of a composite Internet of Things (IoT) to relay packet signals in real-time with Hbb Broadcasting frequency signals routed through ezy-proxies and our respective Universities for Institution-wide, minimal labour hour information systems administration to maximise positive outcomes of student, faculty, library and student administration for protocol pedagogy and intranet-directed Strategic Management of student and faculty support and services as an alternative to reduce discrete-object administrative and learning material delivery inefficiencies as has been found with third-party LMS such as WebCT and Blackboard through our Universities electronic auto-compiling object errors as is a current area of research in software API universal framework alignment, and primary objective labour hours for increased Research and Institution-wide revenue raising of objective reduction in student intake population numbers to benefit both student study and reading and also commercial intellectual property of private-sponsored research at The University of Western Australia and Harvard University. I am also interested in

SQL Server has been ported to Linux for over a year now and it is time the complete SMO library (or what can be) is ported over to cross-platform as well.

Only 9 or so core files have been ported over to .NET Core and this allowed the sqlserver module to port over a small set of cmdlets to PS Core. This does not work for other modules like dbatools that use a wider berth of the library.

There are plenty of other modules in PowerShell (and applications too) that would like to provide cross-platform support for managing SQL Server enterprises. This cannot be done until SMO is completely ported over.

When RAID controllers are idle, they automatically check the storage to make sure it's still okay. Why not SQL Server too?

Some of the pieces are there – for example, SQL Server already has the ability to watch for idle CPU times and run Agent jobs when it’s bored. For starters, that’d probably be good enough to save a lot of small businesses from heartache. For the databases over, say, 100GB, it’d be really awesome to have resumable physical_only corruption checking – tracking which pages have been checked (just like how the differential bitmap tracks page changes), with page activity reset when the page is changed (again, just like the differential bitmap.) This wouldn’t count the same as a real CHECKDB, which needs to do things like compare index contents – but it'd be a big improvement over what we have now in environments where folks just aren't aware that the onus for data integrity is on them, not SQL Server.

If a query uses one or more partitioned tables that use incremental statistics and whose partition function has been modified using the MERGE and SPLIT partition commands, a connection-terminating access violation can occur when the incremental statistics need to be automatically updated during plan compilation.

The attached script reliably reproduces the error on multiple SQL Server 2017 database servers we've tried thus far, including a server running CU11. We've also attached dump files from both a real production occurrence of this error and a testing occurrence of the error using our repro script.

SQL Server 2017 CU8 contained a fix to what might be a related problem: https://support.microsoft.com/en-us/help/4163478/fix-access-violation-when-incremental-statistics-automatically-updated However, we are still hitting the access violation on servers with both SQL Server 2017 CU9 and SQL Server 2017 CU11 (the most recent CU at this time), so it looks like we've found another (potentially related) access violation bug that has not yet been addressed.

This bug only reproduces if the COMPATIBILITY_LEVEL is 140 (SQL Server 2017). We have not been able to reproduce the bug using COMPATIBILITY_LEVEL 130. We have also not been able to reproduce in SQL Server 2016 SP2. Based on these observations, this appears to be a new bug introduced in SQL Server 2017.

The bug also cannot be reproduced if AUTO_UPDATE_STATISTICS_ASYNC is turned ON for the database. This is the workaround we've been using for now, but it is not ideal because this is a fairly large change to make that will require a lot of testing and might not be suitable for all our databases.

There is a bug in SQL Server Management Studio (17.9 and all below) that force the application to crash/restart. In order to reproduce follow the steps below:

1. Select database from the object explorer
2. Press F7 to open Object Explorer Details window and perform a search to object
3. After the search completes, select the object, right click on it and then click "synchronized" from the menu.
4. Then click the `BACK` button several times (fast). You will get the following error:

"There is already a commandd handler for the menu command 'guid goes here: 189."

After several clicks somewhere other the SSMS will crash and restart. Check the screenshots, too.

The following query performs a windowed SUM over a columnstore table with 1500 total rows, each of which has the value 0 or 1, and it overflows the INT data type. This appears to be a bug in the batch mode window aggregate operator.

SELECT a, p, s, v, m, n,
SUM(CASE WHEN n IS NULL THEN 0 ELSE 1 END)
OVER (PARTITION BY s, v, a ORDER BY p) AS lastNonNullPartition
FROM (
SELECT a, p, s, v, m, n,
RANK() OVER (PARTITION BY v, s, a, p ORDER BY m) AS rank
FROM #t /* A columnstore table with 1,500 rows */
) x
WHERE x.rank = 1
--Msg 8115, Level 16, State 2, Line 1521
--Arithmetic overflow error converting expression to data type int.

If any of the following modifications are made, the error does not occur:

* Use trace flag 8649 to prefer a parallel plan regardless of the cost threshold for parallelism
* Use trace flag 9453 to disable batch mode
* Use the COUNT aggregation function instead of the SUM function
* Remove the WHERE x.rank = 1 predicate

See https://dba.stackexchange.com/questions/218634 for many more details and comments.

See https://gist.github.com/pattertall/2875082fe045c90b253c24a954d4f6fc (or the attached file) for a full reproduction script. This bug reproduces in SQL Server 2016, 2017, and 2019 CTP.

The last two lines will not return anything. For all other letters of the Cyrillic alphabet, this is not the case.
This is an old discrepancy in the Ukrainian_100_CI_AS encoding and similar.
Perhaps in UTF8 it is worth changing the behavior as in SQL_Ukrainian_CP1251_CI_AS?

select serverproperty('Collation')
exec sp_helpsort

create table #x (
a varchar(10) collate SQL_Ukrainian_CP1251_CI_AS
, b varchar(10) collate Ukrainian_100_CI_AS_SC_UTF8
, c varchar(10) collate Ukrainian_100_CI_AS
)

declare @x varchar(2) = char(252) + char(252) --ьь
declare @y varchar(2) = char(252) + char(220) --ьЬ

select @x, @y

insert into #x select 'ьЬ', 'ьЬ', 'ьЬ'
select * from #x where a like '%ьь%'
select * from #x where b like '%ьь%'
select * from #x where c like '%ьь%'

drop table #x

------ RESULT:

--------------------
SQL_Ukrainian_CP1251_CI_AS

(1 row affected)

Server default collation

--------------------

Ukrainian, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 108 on Code Page 1251 for non-Unicode Data

---- ----
ьь ьЬ

(1 row affected)

(1 row affected)

a b c
---------- ---------- ----------
ьЬ ьЬ ьЬ

(1 row affected)

a b c
---------- ---------- ----------

(0 rows affected)

a b c
---------- ---------- ----------

(0 rows affected)

Executing a query with an OUTER JOIN can cause the cardinality estimator to expect rows being filtered out. This should never be the case if we're doing an OUTER JOIN and can result in performance issues as the row set and memory needed for downstream operators is underestimated.

Attached is a reproduction script and some sample data. A few additional observations:
- This seems to happen when the dimension has a higher cardinality than the fact table. Perhaps not the main use case, but we have financials where codes may be added/removed over time, while the dimension table will contain all the historical codes.
- When running with trace flags 2363 and 3604, the selectivity computation output showed lines where we were scaling the join selectivity up - "Scaling join selectivity up by X to compensate for more distinct values in dimension than in fact". This make sense for an INNER JOIN, but seems to be a bug for OUTER JOIN.
- When reverting to the legacy cardinality estimator using, this behavior is fixed.

what is ssms:

SSMS is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. SSMS provides tools to configure, monitor, and administer instances of SQL. Use SSMS to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts.

--> build queries and scripts

if you remove debugging from ssms --> https://cloudblogs.microsoft.com/sqlserver/2018/10/03/ssms-18-0-public-preview-released/

ssms will be degraded to an simple editor with some nice helpers to write sql but not an integrated enveronment to write scripts and common database objects.

every developer will write good and working code, but sometimes the developer need help. this help will be provided by eg an debugger. and the debugging stuff is one of the most important woolset what every! serious developer need. ssms is not an admin ui to manipulate database objects and so on. it is a very good tool to write tsql scripts, functions and so on. and exact at this place the developer (like me) need help. eg: if you write an udf with some complex code and you need deeper informations inside during runtime --> what is the way to get this infos --> use an debugger! --> if you don't have an debugger, the developer can use the print functions --> but this a real, real bad idea for serious development --> so pls try using print at an udf --> it's not allowed --> bingo --> so you have to change the function to an procedure to use printinf for debugging. real, real horrible and follow up, it makes degrade this tool to an admin script tool and it lost an great and very essential feature, which is useful for every serious developer (and also admin)! pls think about this decision! thanks dietmar

Following on from a conversation on https://www.powershellgallery.com/packages/Sqlserver/21.0.17279
The -Database parameter on the Invoke-SqlCmd cmdlet takes a [string] as its input, but ideally should be able to cope with receiving the output object from the Get-SqlDatabase cmdlet.
As the -Instance parameter does successfully take the output of the Get-SqlInstance cmdlet, I assume this is a bug.
Issue can be reproduced like so:

$SQLCred = Get-Credential -UserName "dbUser"

$instance = Get-SqlInstance 192.168.1.100 -Cred $SQLCred #Works fine

$db = Get-SqlDatabase -Name "test_db" -ServerInstance $instance #Works fine

$results = Invoke-SqlCmd -Database $db -ServerInstance $Instance -Query "Select column FROM view" -Cred $SqlCred # Throws that "[test_db]" cannot be found

Can be worked around by using "-Database $db.Name"