I'm trying to trouble shoot a slow performing query using Show Plan Analysis (SSMS) on the actual execution plan. The Analysis tool points out that estimates for number of rows are off from returned results in a few places in the plan and further gives me some implicit conversion warnings.
I don...
He added a query plan and table definitions for two of the tables. It looks like the columns match to me, so I don't know what those warnings on the select operator are all about.
I tried to focus in on one of the warnings, [ccd].[profileid]. It's used twice, joining to two other tables that have a profileid column. Those are the 3 tables posted. All of them are ints.
Thus I'm puzzled by the implicit conversion warning.
I don't understand what you mean about the transitive property.
But thanks for taking a glance at it, @Joe!
Brent mentioned you alongside Niko as a columnstore expert in the training today.
The implicit conversions are caused by the computed column AltKey:
CREATE TABLE dbo.Test
(
[sessionid] [decimal](18, 0) NOT NULL,
[sessionseqnum] [smallint] NOT NULL,
[nodeid] [smallint] NOT NULL,
[profileid] [int] NOT NULL,
[AltKey] AS
CONCAT
(
[...
@ErikDarling I'm about to go back into class, I should probably pay attention so I don't fall further behind. I found the parameter sniffing lab to be very challenging. I'll ping you about it later.
create trigger MyTrigger on myTable
after update
as
begin
set nocount on;
update talleres set status='active' where FirstDate=getdate()
end
go
create trigger MyTrigge2 on MyTable
for update
as
begin
declare @d DATETIME=getdate();
set nocount on;
update talleres set status='Active...
room topic changed to stop the merry-go-round: Gallery, but feel free to request write access if you read SQL Server CU fixes for fun [database-internals] [sql-server]
room topic changed to stop the merry-go-round: 🤔🤔🤔 Interrogate Erik, Friday at noon EST: youtu.be/YFUEvMS7PtA 🤔🤔🤔 Gallery, but feel free to request write access if you read SQL Server CU fixes for fun [database-internals] [sql-server]
lol. This is the kind of funk I was alluding to... although I like the idea of stink:
> Funk is a music genre that originated in African American communities in the mid-1960s when African American musicians created a rhythmic, danceable new form of music through a mixture of soul music, jazz, and rhythm and blues.
A simple summary of my question is: What is the current best practice for scaling out a MS SQL server enterprise wide OLTP web application to cope with potentially ten thousand users around the globe?
Much of the info online and similar questions date back several years, and I'm not sure what is...
Some would say I'm hardcore. Others would say I'm bad with money.
I just like trying old games. It's fun.
I really thought I'd be right with that Tales of Vesperia. Type of game that ends up not having enough copies because Namco Bandia has no fucking clue what they're doing.
Coming to SQL from other programming languages, the structure of a recursive query looks rather odd. Walk through it step by step, and it seems to fall apart.
Consider the following simple example:
CREATE TABLE #NUMS
(
N BIGINT
)
;
INSERT INTO #NUMS
VALUES
(3),
(5),
(7)
;
WITH R AS
(
...
@jadarnel27 as an absolute and complete guess, I'd say some form of halloween protection might be involved. 95% likely I'll be proven totally wrong, though.
That, and a cursor, for good measure.
As @PaulWhite once said, trust me to make it into a cursor.
The implicit conversions are caused by the computed column AltKey:
CREATE TABLE dbo.Test
(
[sessionid] [decimal](18, 0) NOT NULL,
[sessionseqnum] [smallint] NOT NULL,
[nodeid] [smallint] NOT NULL,
[profileid] [int] NOT NULL,
[AltKey] AS
CONCAT
(
[...
create trigger MyTrigger on myTable
after update
as
begin
set nocount on;
update talleres set status='active' where FirstDate=getdate()
end
go
create trigger MyTrigge2 on MyTable
for update
as
begin
declare @d DATETIME=getdate();
set nocount on;
update talleres set status='Active...
Coming to SQL from other programming languages, the structure of a recursive query looks rather odd. Walk through it step by step, and it seems to fall apart.
Consider the following simple example:
CREATE TABLE #NUMS
(
N BIGINT
)
;
INSERT INTO #NUMS
VALUES
(3),
(5),
(7)
;
WITH R AS
(
...
