SQL Server

Microsoft SQL Server 2017 powers your entire data estate by supporting structured and unstructured data sources. It builds on previous versions of SQL Server, which have been industry leading for four years in a row and a leader in TPC-E. It scales to petabytes of data and allows customers to process big data through PolyBase using T-SQL over any data. SQL Server has also been the least vulnerable database during the last seven years. SQL Server 2017 brings data insights with business intelligence capabilities that provide analytics at a fraction of the cost on any device along with advanced analytics with support for R and Python.

More details about SQL Server are available in the SQL Server documentation.
If you have a technical issue, please open a post on the developer forums through Stack Overflow or MSDN.

Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

SSMS 18.1 Crashes when Opening a Database Diagram

SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.

I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.

You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.

Latest bits for SSMS and SQL Server 2017 installed today.

SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.18362

SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.

I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.

You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.

Latest bits for SSMS and SQL Server 2017 installed today.

SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET…

513 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

270 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →

started · AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) responded

Good news (I hope)!

I was finally able to make progress on this. On the machine with the fix, I was able to open a diagram created by SSMS 17.9.1 (on a different machine). The same diagram opened with 18.3.1 resulted in a crash.

I’ll do more testing in the next few days and go over all the comments on this page to make sure I capture all the scenarios and make sure they are really fixed.

It’s looking good, I really hope… :)

-Matteo
Trace Flag/sp_configure Option to Allow Developer or Evaluation Editions to "Act" like Standard Edition

One of the challenges for many customers who need to use Standard Edition is that both Developer and Evaluation Editions of SQL Server are the same functionally as Enterprise Edition. This means that in non-production scenarios/environments, without buying a full license of Standard Edition (or having MSDN), you are potentially using (or able to use) features not available in Standard. Dev and Eval should have a way to allow those who will ultimately be using Standard to constrain what features are used as well as any performance limitations in Standard so their eval/dev/testing efforts are accurate.

208 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

16 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →

under review · AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) responded

Thank you for filing this feedback item. We will evaluate this for the next major release of SQL Server.
SSMS 18.0 redraw issues when switching between multiple query windows
SSMS 18.0 redraw issues when switching between multiple query windows

Repro:
1. Open SSMS
2. Open a new query window and enter and execute a command, such as:

SELECT @@SPID;

Open a second query window

Using your mouse, switch back and forth between the two open query windows by clicking on their tabs.

After several clicks (five to ten?), the content of the first window (query and result pane) may appear to be displayed in the second window, but you can't interact with any of the text.

Switching back and forth a few more times may clear up the issue temporarily.

The same issue may carry over to additional query windows which are opened, after switching between the various windows several times.
SSMS 18.0 redraw issues when switching between multiple query windows

Repro:
1. Open SSMS
2. Open a new query window and enter and execute a command, such as:

SELECT @@SPID;

Open a second query window

Using your mouse, switch back and forth between the two open query windows by clicking on their tabs.

After several clicks (five to ten?), the content of the first window (query and result pane) may appear to be displayed in the second window, but you can't interact with any of the text.

Switching back and forth a few more times may clear up the issue…
310 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

94 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) responded

Thanks everybody for providing the list. I’ve passed the info to the Visual Studio Team.

In the meanwhile, I have 2 more requests:
1) If you happen to have Visual Studio 2017 (version 15.9.11 or greater), could you check and see if it shows the same behavior?
2) If you happen to have SSMS 17.9.1 on the same machine, could you check and see if it shows the same behavior?

I’m hearing from folks here that “changing SSMS such that it disables h/w acceleration by default” is not a recommended thing to do… However, quite honestly, at this point, it may be the only option I can think about.. :-(

-Matteo
SQL Server vNext (post 2019) and NoSQL functionality

Hello,

This is an invitation for discussion to the SQL Server engine team and the community.

IMHO, SQL Server vNext (post 2019) should beef up its NoSQL functionality.
Specifically, its XML APIs.
This area is dormant since 2005/2008 release.

SQL Server currently supports the following:
- a subset of XQuery 1.0, circa 2007
- a subset of XPath 2.0, circa 2007
- XSD 1.0 circa 2001

The current w3c standards:
- XQuery 3.1
- XPath 3.1
- XSD 1.1 circa 2012

Everything is in place, even current support for the UTF-8 encoding in 2019.

Famous Obamacare is implemented by using MarkLogic as its DB, since the initial relational Oracle DB implementation failed the mission.

Just imagine if it had been MS SQL Server.
SQL Server is ready to move beyond pure relational DB.

Hello,

This is an invitation for discussion to the SQL Server engine team and the community.

IMHO, SQL Server vNext (post 2019) should beef up its NoSQL functionality.
Specifically, its XML APIs.
This area is dormant since 2005/2008 release.

SQL Server currently supports the following:
- a subset of XQuery 1.0, circa 2007
- a subset of XPath 2.0, circa 2007
- XSD 1.0 circa 2001

The current w3c standards:
- XQuery 3.1
- XPath 3.1
- XSD 1.1 circa 2012

Everything is in place, even current support for the UTF-8 encoding in 2019.

Famous Obamacare is implemented by using…

179 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

30 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
Add support for Row Pattern Recognition in T-SQL (SQL:2016 features R010 and R020)
The ISO/IEC 9075:2016 standard (aka SQL:2016) introduces support for Row Pattern Recognition (RPR) in SQL. Similar to using regular expressions to identify patterns in a string, RPR allows you to use regular expressions to identify patterns in a sequence of rows.
To me, it's the next step in the evolution of window functions. If you think that window functions are profound and useful, RPR is really going to bake your noodle.
RPR has limitless practical applications, including identifying patterns in stock market activity, handling time series, fraud detection, material handling, shipping applications, DNA sequencing, gaps and islands, top N per group, and many others.
Similar to window functions, RPR supports partitioning and ordering, which are the basis for finding a pattern in a given sequence of rows, within the indicated partitions, based on the indicated ordering. Also similar to window functions, this feature lends itself for good optimization, with the ability to rely on index ordering to avoid sorting the data.
You can find coverage of the feature including examples in a 90-page technical report ISO/IEC TR 19075-5, available for free here:
https://standards.iso.org/ittf/PubliclyAvailableStandards/c065143ISOIECTR19075-5_2016.zip
You can also find it as part of the SQL:2016 Part 2: Foundation document, available for purchase here: https://www.iso.org/standard/63556.html
I also provide a summarized coverage of this feature in an article (publication date April 10, 2019) here:
https://sqlperformance.com/2019/04/t-sql-queries/row-pattern-recognition-in-sql

SQL:2016 defines two RPR-related features:
Feature R010, “Row pattern recognition: FROM clause”
Feature R020, “Row pattern recognition: WINDOW clause”
R010 defines a clause/table operator called MATCH_RECOGNIZE, which you apply to an input table or table expression in the FROM clause, and you get a virtual table as output. The context is similar to that of other table operators like APPLY, PIVOT and UNPIVOT. Here’s the general form of a query using this feature:

SELECT <selectlist>
FROM <sourcetable>
MATCH_RECOGNIZE
(

<match_recognize specification>

) AS <table_alias>;

As an example adapted from the aforementioned technical report, suppose that you’re given a table dbo.Ticker, with columns symbol, tradedate and price. The following query identifies V shapes in the stock prices (period with strictly falling price followed by period with strictly increasing price):

SELECT
MR.symbol, MR.matchnum, MR.startdate, MR.startprice,
MR.bottomdate, MR.bottomprice, MR.enddate, MR.endprice, MR.maxprice
FROM dbo.Ticker
MATCH_RECOGNIZE
(

PARTITION BY symbol ORDER BY tradedate MEASURES MATCH_NUMBER() AS matchnum, A.tradedate AS startdate, A.price AS startprice, LAST(B.tradedate) AS bottomdate, LAST(B.price) AS bottomprice, LAST(C.tradedate) AS enddate, -- same as LAST(tradedate) LAST(C.price) AS endprice, MAX(U.price) AS maxprice -- same as MAX(price) ONE ROW PER MATCH -- default AFTER MATCH SKIP PAST LAST ROW -- default PATTERN (A B+ C+) SUBSET U = (A, B, C) DEFINE -- A defaults to True, matches any row B AS B.price < PREV(B.price), C AS C.price > PREV(C.price)

) AS MR;

The PARTITION BY clause defines that you want to handle each stock symbol separately.
The ORDER BY clause defines ordering based on trade date.
The MEASURES clause defines measures that you want to compute for each match for the pattern.
ONE ROW PER MATCH means that the result table will have one row per pattern match, similar to the outcome of grouping. The alternative is ALL ROWS PER MATCH where you want the detail rows returned per pattern match.
AFTER MATCH SKIP PAST LAST ROW means that once a match is found, you want the next attempt to find a match to start after the last row of the current match. There are other alternatives like looking for the next match in the row following the first row of the current match (SKIP TO NEXT ROW), and others.
The DEFINE clause defines row pattern variables representing the different subsequences of rows in the pattern. In the above example A represents any row as a starting point, B represents a subsequence of decreasing prices (B.price < PREV(B.price)), and C represents a subsequence of decreasing prices (C AS C.price > PREV(C.price)).
The PATTERN clause uses regular expressions to identify a pattern. In the above query the pattern is (A B+ C+), meaning (any row, followed by one or more rows with increasing prices, followed by one or more rows with decreasing prices). By default the quantifiers are greedy, but you can define them to be reluctant.
Here’s the expected output of this query:

symbol matchnum startdate startprice bottomdat bottomprice enddate endprice maxprice

STOCK1 1 2019-02-13 151.00 2019-02-18 142.00 2019-02-20 152.00 152.00
STOCK1 2 2019-02-27 154.00 2019-03-04 140.00 2019-03-06 143.00 154.00
STOCK2 1 2019-02-14 329.00 2019-02-18 325.00 2019-02-20 328.00 329.00
STOCK2 2 2019-02-21 326.00 2019-02-25 317.00 2019-02-27 325.00 326.00
STOCK2 3 2019-03-01 324.00 2019-03-05 319.00 2019-03-07 326.00 326.00

R020 uses row pattern recognition as part of the windowing OVER clause (or WINDOW clause when naming a window specification) to further restrict a window frame. Just like the window partition restrict the rows of the input table expression (FROM…WHERE…GROUP BY….HAVING), and the window frame further restricts the window partition, with R020 you further restrict the window frame to the first pattern match in the windowed sequence of rows. Here’s a query demonstrating this:

SELECT T.symbol, T.tradedate, T.price,
startdate OVER W, startprice OVER W,
bottomdate OVER W, bottomprice OVER W,
enddate OVER W, endprice OVER W,
maxprice OVER W
FROM dbo.Ticker T
WINDOW W AS
(

PARTITION BY symbol ORDER BY tradedate MEASURES A.tradedate AS startdate, A.price AS startprice, LAST(B.tradedate) AS bottomdate, LAST(B.price) AS bottomprice, LAST(C.tradedate) AS enddate, -- same as LAST(tradedate) LAST(C.price) AS endprice, MAX(U.price) AS maxprice -- same as MAX(U.price) ROWS BETWEEN CURRENT ROW -- RANGE and GROUPS are not permitted with row pattern matching in windows AND UNBOUNDED FOLLOWING AFTER MATCH SKIP PAST LAST ROW INITIAL -- pattern must start at first row of full window frame; alternative is SEEK PATTERN (A B+ C+) SUBSET U = (A, B, C) DEFINE -- A defaults to True, matches any row B AS B.price < PREV(B.price), C AS C.price > PREV(C.price)

);

Currently, the only platform I know of that implements R010 is Oracle. I don’t know of any platform that implements R020 yet.
It’s completely understood that for Microsoft to add a feature to T-SQL—especially such a substantial one—is a pretty significant investment. But what’s great about features that are added to T-SQL is that they pretty much stay there forever. There’s a huge community hungry for T-SQL improvements such as this one.

Thanks for your consideration!
Itzik
The ISO/IEC 9075:2016 standard (aka SQL:2016) introduces support for Row Pattern Recognition (RPR) in SQL. Similar to using regular expressions to identify patterns in a string, RPR allows you to use regular expressions to identify patterns in a sequence of rows.
To me, it's the next step in the evolution of window functions. If you think that window functions are profound and useful, RPR is really going to bake your noodle.
RPR has limitless practical applications, including identifying patterns in stock market activity, handling time series, fraud detection, material handling, shipping applications, DNA sequencing, gaps and islands, top N per…
307 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

8 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
SSMS Crash when dragging table from Object explorer into new query window

Have just installed this version v18.1 and everytime I drag a table from Object explorer into new query window SSMS crashes, I have to kill it.
I have no add-ins installed, have rebooted since installing.

O/s Win 10 15063.1387

125 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

58 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →

started · AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) responded

Issue has been identified and a fix is being made. It will be rolled out with the next update of SSMS 18.

Thanks,
-Matteo
Put Debugger back into SSMS 18

Debugger please

105 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

28 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
Restore a table from a backup

Hi Msft team!
I'm writing to reccomending a new feature that will help us a lot! Every time that we have data issues (truncate or DML by accident) we need to restore the entire database or filegroup and that takes a lot of time! it will be awesome if you can add the posibility to restore a table from a backup or restore to a point in time directly from SSMS instead off the whole process.
I hope this helps!
Thank you!

724 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

89 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
Add support for standard nested window functions in T-SQL
The ISO/IEC SQL:2016 standard defines a concept called nested window functions that allows you to nest two kinds of window functions as an argument of a window aggregate function. The idea is to allow you to interact with row markers representing strategic points in windowing elements like the beginning or end of the partition, beginning or end of the frame, the current outer row, and the current inner frame row.
The two standard nested window functions are the nested row number function and the nested value_of expression at row function.
The former allows you to refer in an argument of a window aggregate function to a row number at a specified row marker. Here’s the syntax of the nested row number function:

<aggfunc>(< argument with ROWNUMBER(<row marker>) >) OVER(<specification>)

You can use the following row markers:
• BEGINPARTITION
• ENDPARTITION
• BEGINFRAME
• ENDFRAME
• CURRENTROW (current outer row)
• FRAMEROW (current inner frame row)

As an example for using a nested row number function, consider the following query against the Sales.OrderValues view (ER diagram can be found here: http://tsql.solidq.com/SampleDatabases/Diagrams/TSQLV5.jpg ) in the TSQLV5 sample database (source code can be found here: http://tsql.solidq.com/SampleDatabases/TSQLV5.zip):

SELECT orderid, custid, orderdate, val,
val -

AVG( CASE WHEN ROW_NUMBER(FRAME_ROW) NOT IN ( ROW_NUMBER(BEGIN_PARTITION), ROW_NUMBER(END_PARTITION) ) THEN val END ) OVER( PARTITION BY custid ORDER BY orderdate, orderid ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING ) AS diff

FROM Sales.OrderValues;

This query computes the difference between the current order value, and the customer average, but excluding the customer’s first and last orders from the average.
As for the nested value_of expression at row function, this function allows you to interact in an argument of a window aggregate function with the value of an expression at any of the aforementioned row markers. Here’s the syntax of the function:

<agg_func>(< argument with
VALUE OF <expression> AT <row marker> [<delta>] [, <default>]

>) OVER(<specification>)

As you can see, you can specify a certain negative or positive delta with respect to the row marker, and optionally provide a default value in case a row doesn’t exist at the specified position.
As an example, suppose you wanted to compute the difference between the current order value, and the customer’s average, but excluding orders placed on the current order’s order date. What you need is something similar to a correlation within the window function. By referring to the row marker CURRENT_ROW, you interact with the current outer row, and this way you can emulate a correlation. Here’s the query that you would use to achieve this task:

SELECT orderid, custid, orderdate, val,
val - AVG( CASE WHEN orderdate <> VALUE OF orderdate AT CURRENT_ROW THEN val END )

OVER( PARTITION BY custid ) AS diff

FROM Sales.OrderValues;

The other useful thing about nested window functions is that you can use them to emulate full support for the RANGE window frame unit, which is missing in T-SQL. For example, according to the standard, you can use the following query to return the moving average order value of the customer’s orders in the last 14 days:

SELECT orderid, custid, orderdate, val,
AVG(val) OVER( PARTITION BY custid ORDER BY orderdate

RANGE BETWEEN INTERVAL '13' DAY PRECEDING AND CURRENT ROW ) AS movingavg14days

FROM Sales.OrderValues;

But this syntax isn’t supported in T-SQL. If we had support for nested window functions, you would have been able to achieve the task like so:

SELECT orderid, custid, orderdate, val,
AVG( CASE WHEN DATEDIFF(day, orderdate, VALUE OF orderdate AT CURRENT_ROW) BETWEEN 0 AND 13 THEN val END )

OVER( PARTITION BY custid ORDER BY orderdate RANGE UNBOUNDED PRECEDING ) AS movingavg14days

FROM Sales.OrderValues;

These functions seem to be very powerful, and it would be good to have support for them in T-SQL.
Thanks for your consideration!
The ISO/IEC SQL:2016 standard defines a concept called nested window functions that allows you to nest two kinds of window functions as an argument of a window aggregate function. The idea is to allow you to interact with row markers representing strategic points in windowing elements like the beginning or end of the partition, beginning or end of the frame, the current outer row, and the current inner frame row.
The two standard nested window functions are the nested row number function and the nested value_of expression at row function.
The former allows you to refer in an argument of…
119 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

8 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
SQL 2019 15.0.2070.41: Out of memory, page allocation fails when using Scalar-valued function in Where -clause

Instance crashes to OOM using Scalar-valued functions when Scalar UDF Inlining is turned ON and function is used on WHERE -clause. Not dependent on SQL memory as it always consumes all memory available to instance.

Simple function (i.e returning date) fails when used on WHERE clause and page allocation from MEMORYCLERKSQLOPTIMIZER allocates all memory even with fresh database when TSQL-SCALARUDF_INLINING is ON.

Working query with function:
declare @dt as datetime='2019-12-01'
declare @dt2 as datetime='2019-12-20'
declare @d as datetime = dbo.datereturn(@dt2,'ENDOFDAY')
select * from TABLE where field_date between @dt and @d

Broken query with function in WHERE -clause:
declare @dt as datetime='2019-12-01'
declare @dt2 as datetime='2019-12-20'
select * from TABLE where field_date between @dt and dbo.datereturn(@dt2,'ENDOFDAY')

Later query works when TSQLSCALARUDF_INLINING is set OFF

Instance crashes to OOM using Scalar-valued functions when Scalar UDF Inlining is turned ON and function is used on WHERE -clause. Not dependent on SQL memory as it always consumes all memory available to instance.

Simple function (i.e returning date) fails when used on WHERE clause and page allocation from MEMORYCLERKSQLOPTIMIZER allocates all memory even with fresh database when TSQL-SCALARUDF_INLINING is ON.

Working query with function:
declare @dt as datetime='2019-12-01'
declare @dt2 as datetime='2019-12-20'
declare @d as datetime = dbo.datereturn(@dt2,'ENDOFDAY')
select * from TABLE where field_date between @dt and @d

Broken query with function in WHERE -clause:
declare…

24 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · Bugs · Flag idea as inappropriate… · Delete… · Admin →
Debugger in SSMS 18.0 and above versions.

It is very disappointing that Microsoft has removed debugger in SSMS 18.0+ versions. In an alternative Visual Studio can debug the SQL stored procedures. But we cannot install Visual studio in customer server PC's for sql debugging. Please add back debugger in SSMS.

31 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

2 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
Fix SSMS open diagram crash

1) Create diagram
2) Close SSMS
3) Open SSMS
4) Open diagram
5) SSMS silence crash

31 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

8 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →
SQL Server 2019 Snapshot Agent Error

I was trying to configure an SQL Server 2019 transactional replication, but the snapshot agent returns an error. Running it from command line i got the folloing error:

2019-12-18 12:54:33.91 Command Text: select count_big() from sys.tables
2019-12-18 12:54:33.91 Parameters:
2019-12-18 12:54:33.91 [0%] The replication agent had encountered an exception.
2019-12-18 12:54:33.91 Source: Replication
2019-12-18 12:54:33.91 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
2019-12-18 12:54:33.91 Exception Message: An unspecified error had occurred in the native SQL Server connection component.
2019-12-18 12:54:33.91 Message Code: 55012
2019-12-18 12:54:33.91

2019-12-18 12:54:33.91 Call Stack:
2019-12-18 12:54:33.91 Microsoft.SqlServer.Replication.ReplicationAgentException: An unspecified error had occurred in the native SQL Server connection component.
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection pNativeConnectionWrapper)
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowConnectionFailureException(CConnection* pNativeConnectionWrapper)
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.InitializeNativeBcpOutProvider(LogMessageCallback logMessageCallback, String strName, String strApplication, String strHost, String strServer, String strNetwork, Int32 encryptionLevel, String strDatabase, SecurityMode securityMode, String strLogin, SecureString strPassword, Int32 bcpBatchSize, Int32 loginTimeout, Int32 queryTimeout, Int32 packetSize, DeadlockPriority deadlockPriority, String strRowDelimiter, String strFieldDelimiter, Byte syncMethod, Boolean forceOdbcBcp, Boolean forceOleDbBcp, Boolean enableMultipleActiveResultSets, Boolean useReadPastHint, Boolean usePageLockHint, Boolean securePassword)
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.TransSnapshotProvider.InstantiateBcpOutProviderWorker(String strBcpConnectionName)
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.InstantiateBcpOutProvider(String strBcpConnectionName)
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.Initialize()
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
2019-12-18 12:54:33.91 at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper()
2019-12-18 12:54:33.91 [0%] The replication agent had encountered an exception.
2019-12-18 12:54:33.91 Source: Replication
2019-12-18 12:54:33.91 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
2019-12-18 12:54:33.91 Exception Message: An unspecified error had occurred in the native SQL Server connection component.
2019-12-18 12:54:33.91 Message Code: 55012

I've already installed the last version of OLE DB.

Thank you for any help.

Best regards,
José Cruz

I was trying to configure an SQL Server 2019 transactional replication, but the snapshot agent returns an error. Running it from command line i got the folloing error:

2019-12-18 12:54:33.91 Command Text: select count_big() from sys.tables
2019-12-18 12:54:33.91 Parameters:
2019-12-18 12:54:33.91 [0%] The replication agent had encountered an exception.
2019-12-18 12:54:33.91 Source: Replication
2019-12-18 12:54:33.91 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
2019-12-18 12:54:33.91 Exception Message: An unspecified error had occurred in the native SQL Server connection component.
2019-12-18 12:54:33.91 Message Code: 55012
2019-12-18 12:54:33.91

2019-12-18 12:54:33.91 Call Stack:
2019-12-18 12:54:33.91 Microsoft.SqlServer.Replication.ReplicationAgentException: An unspecified error had occurred in the native SQL Server connection…

14 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

7 comments · Other · Flag idea as inappropriate… · Delete… · Admin →
SQL Server Management studio for Windows on ARM (ARM64)

The Surface Pro X received a lukewarm reception for reviewers, but has been consistently sold out and has quite the popularity. More ARM64 apps are needed to truly get this product going

SSMS 18 and 17 cannot install on the Surface Pro X. The installer runs, but fails due to architecture. Going back to a build of SSMS from the past, SSMS 16, allows me to install it, but I'm missing the newer features.

Could we please get a build of SSMS for ARM64? I can't imagine this would be a difficult task given Visual Studios ability to compile for Windows on ARM straight out the box.

The Surface Pro X received a lukewarm reception for reviewers, but has been consistently sold out and has quite the popularity. More ARM64 apps are needed to truly get this product going

SSMS 18 and 17 cannot install on the Surface Pro X. The installer runs, but fails due to architecture. Going back to a build of SSMS from the past, SSMS 16, allows me to install it, but I'm missing the newer features.

Could we please get a build of SSMS for ARM64? I can't imagine this would be a difficult task given Visual Studios ability to compile for…

18 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

4 comments · Other · Flag idea as inappropriate… · Delete… · Admin →
SSMS 18.2 Edit Job Step hangs

In SSMS 18.2 when we edit a job step under Job properties it takes minutes to open the edit box
- editjob.PNG 102 KB
22 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

planned · 14 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →
SQL Server new algorithm to chose NUMA node to bind connection to

When SQL Server is deployed on NUMA hardware or virtual hardware, it binds connections to NUMA nodes in a round robin fashion. This is not correct and often lead to NUMA node imbalance. I suggest to create an algorithm which takes into account the nodes load and choses the least loaded.

27 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

3 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
Add Query IO Stats Roll Up To Query Plans

When you get an actual execution plan in SSMS, the root operator has a QueryTimeStats attribute where you can view CPU and Elapsed Time for your query as a whole.

There are also IO stats per operator, but no roll up at the root node. It would be handy to have this, similar to SET STATISTICS IO ON, so you would know which operators to dig into based on table reads.

Right now, you have to click around to figure anything out, and that can be painful in large execution plans.

10 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

2 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
SSMS add a pane with a vertical list of open queries

In SSMS add a pane with a vertical list of open queries similar to the Object Explorer pane that can be docked/undocked that you can see the entire file name and quickly navigate or choose from the entire list of tabs of open query files to choose from.
I know that on the very right edge of the horizontal list of tabs, there is a drop down arrow that shows the list of tabs vertically but I'd like it to be able to dock like Object Explorer, Registered Servers, etc.
So, instead of horizontal tabs where the file name and other details that are partially hidden or don't appear if many files are open, have an option to show a vertical list of open files.
Add ability to pin so that the pinned ones go to the top of the vertical list.
It should look like the list of Files in the Solution Explorer but only open files.
There is at least one third party company selling a plug-in but who has money for that...
In SSMS add a pane with a vertical list of open queries similar to the Object Explorer pane that can be docked/undocked that you can see the entire file name and quickly navigate or choose from the entire list of tabs of open query files to choose from.
I know that on the very right edge of the horizontal list of tabs, there is a drop down arrow that shows the list of tabs vertically but I'd like it to be able to dock like Object Explorer, Registered Servers, etc.
So, instead of horizontal tabs where the file name and…

27 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

2 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →
BCP always adds a row delimiter after 2022 chars and has a bug when declaring an empty row delimiter
There are a couple of bugs in BCP that don't allow you to extract a proper formatted JSON (or XML) file. In details:

BCP always adds a row delimiter after 2022 chars

BCP uses 63.502 white spaces (0x20) as row delimiter using -c if you pass an empty row delimiter (-r). So you'll find 63.502 white space after 2022 chars and at the end of the string.

BCP uses 63.502 combinations of chars 0x20 and 0x00 as row delimiter using -w if you pass an empty row delimiter (-r). So you'll find 63.502 white space after 2022 chars and at the end of the string.

You can find a repro script as attachment (just remove the dummy ".png" extension from the filename).
There are a couple of bugs in BCP that don't allow you to extract a proper formatted JSON (or XML) file. In details:

BCP always adds a row delimiter after 2022 chars

BCP uses 63.502 white spaces (0x20) as row delimiter using -c if you pass an empty row delimiter (-r). So you'll find 63.502 white space after 2022 chars and at the end of the string.

BCP uses 63.502 combinations of chars 0x20 and 0x00 as row delimiter using -w if you pass an empty row delimiter (-r). So you'll find 63.502 white space after 2022 chars and at…
7 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

4 comments · Bugs · Flag idea as inappropriate… · Delete… · Admin →
Allow Updating Statistics on the Secondary Replicas of the Availability Groups

Allow remote (on the secondary replicas) statistics update for the Availability Groups. Given that a lot of time the secondary replicas have extra resources
Potentially this could lead into spreading & parallelising the statistics recalculation processes while doing maintenance or potentially even ad-hoc.
The original idea behind this is described in the following blogpost – http://www.nikoport.com/2019/06/20/updating-statistics-on-secondary-replicas-of-the-availability-groups/

52 votes

Sign in
prestine

(thinking…)

Sign in with: Microsoft

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

under review · 2 comments · Suggestions · Flag idea as inappropriate… · Delete… · Admin →

← Previous 1 2 3 4 5 … 519 520 Next →

Don't see your idea?

SQL Server

Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

SSMS 18.1 Crashes when Opening a Database Diagram

Trace Flag/sp_configure Option to Allow Developer or Evaluation Editions to "Act" like Standard Edition

SSMS 18.0 redraw issues when switching between multiple query windows

SQL Server vNext (post 2019) and NoSQL functionality

Add support for Row Pattern Recognition in T-SQL (SQL:2016 features R010 and R020)

SSMS Crash when dragging table from Object explorer into new query window

Put Debugger back into SSMS 18

Restore a table from a backup

Add support for standard nested window functions in T-SQL

SQL 2019 15.0.2070.41: Out of memory, page allocation fails when using Scalar-valued function in Where -clause

Debugger in SSMS 18.0 and above versions.

Fix SSMS open diagram crash

SQL Server 2019 Snapshot Agent Error

SQL Server Management studio for Windows on ARM (ARM64)

SSMS 18.2 Edit Job Step hangs

SQL Server new algorithm to chose NUMA node to bind connection to

Add Query IO Stats Roll Up To Query Plans

SSMS add a pane with a vertical list of open queries

BCP always adds a row delimiter after 2022 chars and has a bug when declaring an empty row delimiter

Allow Updating Statistics on the Secondary Replicas of the Availability Groups

Feedback

SQL Server

Feedback and Knowledge Base

Searching…

Give feedback

Microsoft Azure

Your password has been reset

Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

SQL Server

Categories

Searching…

Your password has been reset