Thanks. The SQL servers our company uses runs on version 11.0.x. For my local copy of SSMS, I've been habitually using SQL 2012, which the rest of my team uses. If I installed a more recent version of SQL SSMS, would this be compatible with the database?
The side by side thing might be a good option for me, just in case. I connect to the prod database, so hence the question here, I didn't want to do something that inadvertently upgraded the prod database or something daft like that.
i use to keep pinned the launchers for different major releases of SSMS & BIDS/SSDT and just kept a mental rolodex of which server was running which version so i didn't end up auto-upgrading packages just from opening them up
I use the SSMS that comes with the product. Except for SQL Server 2016+ which doesn't deliver a SSMS with the product. Then I use the current stable release of SSMS 17.*
Noted, thanks for the tip. Really useful stuff from all of you.
Ok, so SQL Server 2014 Management Studio will basically give me the latest release version of SSMS, right? I think that's right. SSMS is one of those things I only install every 5 years or so.
weird question for the room - anyone know if the Brent O weekly links are archived like the blog posts are anywhere other than my gmail recycle bin? like - i'm trying to remember some random post on memory pressure from a month or two ago but I'm pretty sure the original email has aged out of my trash by this point
I trolled back through to June (ish) before I called it. I saved the links though (FB never forgets...) & I've grokked the URL pattern in case I get the gumption to take another crack at it
My old boss emailed me this morning to let me know they finally root-caused a recurring OOM hekaton issue we observed so I'm just sort of info-dumping to see if I can put together something coherent enough to be worth sharing
TL;DR: for the room "Turns out when you delete from an IMO table variable, it wonβt release the deleted rows from memory until the table variable goes out of scope"
You can use not exists with row_number() :
select top (1) with ties t.*
from table t
where not exists (select 1 from table t1 where t1.id = t.id and t1.IS_FINAL = 1)
order by row_number() over (partition by id order by seq desc);
from what I cant tell the user is just looking for distint values where the ID isn't 1 select distinct ID, State from table where IS_Final != 1
@Zane I first saw that trick (SELECT TOP (1) WITH TIES ... ORDER BY ROW_NUMBER() ...) in one of Martin Smith's answers. I actually liked it, to be honest (still do). Not sure how well it performs compared to others, though
Soooo the flaged as Duplicate does not answer the OP's question. He just needs a where cluase and distinct rows via either a group by or a distinct this CTE asks for the top row. This question just wants distinct results where the value isn't 1. — Zane12 secs ago
I'm a huge fan of keeping things simple wherever possible.
You need to exclude a group of rows if at least one of the rows has Is_Final = 1. It's possible to avoid a NOT IN or NOT EXISTS or any other kind of self-ant-join but it still won't be very simple.
yeah he doesn't want both. I missed that part as well. Either way it's been closed. Also I still stand by my that guys solution is insanely overworked. I had a fiddle to do what he wanted but fiddle is borked and the question isn't open anyway
Okay so I've come up with a pretty simple solution that works for you and should be pretty easy to follow. Answer and demo is up top explaination to follow.
create table #SOQ (
ID char(2),
Is_Final smallint,
SEQ int,
State varchar(30))
insert into #SOQ values ('A1', 0 , 12, 'Pen...
Wanted to add more explaination to what I'm doing. Like I said. Dude seems pretty green.
@Snow I've heard of Apex but never used their stuff - how on earth can there be so many options for formatting hahaha. This looks like Ola's scripts if they had a UI
No problem. I just use it because it's free and I'm lazy. And it's good to show off to colleagues that I can format SQL when they just send me free-typed junk.
I found ApexSQL Refactor because I had the hope that it would refactor my queries into more performant code. I since learnt that there's nothing that can do that form of magic.
Ok, gotta hit the road and quit for the weekend. Thanks all for being welcoming and helpful, traits that are sadly lacking in some quarters of the SE network. Hope to see you guys around again soon.
We migrated our platform to new SQL Server 2016 instances a couple of nights ago. Immediately following the migration, we ran sp_Blitz again, but noticed the following entry, which relates to the dedicated volume holding tempdb (all eight data files and the single log file reside on the same dedi...
At my last gig we were getting huge disk latency and the SAN team kept saying that we were fine. I kept pushint and pushing and eventually found out they didn't hook up the cabling we asked and also hadn't striped the drives as per our request. I imagine they're still dealing with that now.
@JoeObbish, does this matter? I am switching between using dbcc traceon and querytraceon constantly and the results seem consistent. I assumed the behaviour of the 2 should be identical — Steven Hsu2 mins ago
lol, came in here - as im watching brent ozar's "how to think like the sql server engine" - to ask what the general opinion toward brent's training materials were to this group
and i see @sp_BlitzErik - hi there, lol
i just registered for the live class season pass the other day. and the recorded classes. super pumped about it all
You can use not exists with row_number() :
select top (1) with ties t.*
from table t
where not exists (select 1 from table t1 where t1.id = t.id and t1.IS_FINAL = 1)
order by row_number() over (partition by id order by seq desc);
Okay so I've come up with a pretty simple solution that works for you and should be pretty easy to follow. Answer and demo is up top explaination to follow.
create table #SOQ (
ID char(2),
Is_Final smallint,
SEQ int,
State varchar(30))
insert into #SOQ values ('A1', 0 , 12, 'Pen...
