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

When having to work with script task or components inside of SSIS it becomes quiet tedious because the loading times are exessive and the functionalities are rather limited.
I would like to propose a new form of Script Task, a Script Task v2 if you will. Instead of just exposing a subset of VS making this Script Task a proper C#/VB.net proj that compiles down to a dll. That has a Main Class that implements an interface that contains a execute-method.
These Projects would be added to the SSIS Solution as seperate Projects offering everything from Nuget to properly allowing Version Control of the code within them. This would also allow proper Code reuse through just allowing the same DLL to be called from different places inside the Control or Data Flow inside the Package and different Packages inside the SSIS Project.
This would add tremendous value for the people with a Software Development background and would support more complex usecases with less friction.

Provide a way to directly write XEvent output directly into a SQL Server database table in a same or different instance and same or different database.

The goal being to be able to not have any events missed but have the entire stream captured to the table and also provide header information for when the capture table was created for easier management and deletion. Ideally there should be a purge task that could be activated to clean out such captures after X days.

XEvents is a great and powerful tool.
Customers should have an easier way to get it directly into SQL Server so they can consume the historization back via normal SQL syntax. XEvent output is structured in nature.

2 new target types in sys.dm_xe_objects would likely be helpful:
synchronous_write_SQL_table
asynchrounous_write_SQL_table

Appropriate Security management would need to be put in place.

At the moment we can set a context_info in the application and collect this context_info in a extended event session for classic stored procedures to create an end-to-end telemetry solution. For each user-click operation we can figure out how much time it took in the application as well as how long the stored procedure call takes as well as how many wait_info events occur related to the stored procedure call.

However this does not work with Native Compiled Stored Procedures as there is no way to correlate the database call from the application with the extended events collected by the XE-session in the backend. (we cannot use the context_info field like we do with traditional stored procedures).

Please provide functionality to allow end to end telemetry monitoring for inmemory stored procedures.

It is often useful, when doing real-time activity monitoring, to be able to understand when workers are spending a long time sitting on the runnable queue after entering a wait state.

This information is available in the on-prem product by using the sys.dm_os_workers DMV, which gives numbers in terms of "ms_ticks." Converting these ticks to actual clock time requires pulling an "ms_ticks" value from the sys.dm_os_sys_info DMV.

Unfortunately, Microsoft pulled the latter DMV from Azure SQL DB, making this information completely inaccessible. And it would be quite useful there, especially when DTU throttling is taking place.

My request is to put back sys.dm_os_sys_info, or if it was removed to hide some information that's too general, at least put back a subset of it including the ms_ticks column (or maybe just the ms_ticks column). That way scripts can work seamlessly both on-prem and in SQL DB.

When conencting for far to

2012 sp3
2014 sp2
2016 sp1

I crash anytime I try to open the scheduler task, I still had a VM with 17.4 and this works correctly on the same versions.

New or already created one. No time to enter or modify as it crash on load.

Event id 1000
Faulting application name: Ssms.exe, version: 2017.140.17230.0, time stamp: 0x5aa77b02
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x15723a35
Faulting process id: 0x163c
Faulting application start time: 0x01d3c19109d5c915
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: unknown
Report Id: b943e485-d868-45b1-832e-09b4f570a55b
Faulting package full name:
Faulting package-relative application ID:

Event id 1000
Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog.InitializeControls()
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog..ctor(Microsoft.SqlServer.Management.SqlMgmt.JobScheduleData)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.ChangeShedule()
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.grid_MouseButtonClicked(System.Object, Microsoft.SqlServer.Management.UI.Grid.MouseButtonClickedEventArgs)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseButtonClicked(Int64, Int32, System.Drawing.Rectangle, System.Windows.Forms.MouseButtons)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.HandleButtonLBtnUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.ProcessLeftButtonUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)

Several users have an error message when they try to create/modify subscriptions with a date parameter that have a default value (using internet explorer).
In the log file of reporting service I see this error:

System.Data.SqlClient.SqlException: Converting a varchar data type to a datetime data type has created a value out of bounds

No problem with Chrome.
Good date format "dd/MM/yyyy". Wrong date format in IE "MM/dd/yy".

I found a workaround with adding French(France) in the languages configuration in IE client. Instead of French(Belgium) wich has a different date format.

Is it possible to configure SSRS to use only server side configured date format ?

Currently, if you force a plan in query store (or if it is forced by automatic plan correction), the exact plan which is forced has is_forced = 1 in sys.query_store_plan. In the plan properties, there is no use_plan indication.

After this plan is forced, often a "morally equivalent" plan will be compiled, which has a different query_plan_id and different costs, but the same plan shape.

This "morally equivalent plan" has is_forced = 0 in sys.query_store_plan. In the execution plan properties, use_plan = true.

These "morally equivalent plans" are currently difficult to identify in the Query Store reports and in the DMVs, because you really have to dig to find the use_plan = true property.

Ideas to improve the user experience:

1) Put some visual indication on a graphic plan on the top left most operator whenever use_plan = true (for whatever reason), to make the fact that something has been forced more obvious

2) Put a check mark (or some indication) on the bubbles in Query Store reports when use_plan = true

3) Make some way to identify these in sys.query_store_plan. (Is_forced = 2?)

Or just anything you can do to make these easier to understand for folks.

More details and a repro script are here: https://sqlworkbooks.com/2018/03/forced-plan-confusion-is_forced-vs-use-plan-true/

Thank you for making SQL Server more awesome!
Kendra