Eirikur Eiriksson (11/10/2016)

---

homebrew01 (11/10/2016)

---

I'm sure it's a long list, but what are the "Top 10" list of improvements I can take to management to help justify spending the $$ to...

1) Indexing a column doesn't mean it will be used for an index seek operation - even if you refactor your WHERE clause as specified. If the optimizer estimates your...

I disagree on the...

EasyBoy (11/8/2016)

---

We have one schedule job which dropping and inserting records into table on daily basis. But this job is failing due to "Could not allocate space for object...

GilaMonster (11/8/2016)

---

I would recommend, instead of creating one trigger FOR INSERT, UPDATE, DELETE, you create three different triggers. One FOR INSERT (which will be fired only for the inserted rows...

dan.brown1 (11/7/2016)

---

I know, it's a kind of silly thing to ask for help without giving more info. We are unfortunate, that our secure ODC blocks all out going traffic, and...

dan.brown1 (11/7/2016)

---

Hi Team,

I'm running a simple SQL query which returns a set of columns based on a search criteria. It has to return 29 rows, but it is giving 0,10,22...

Eric M Russell (11/7/2016)

---

TheSQLGuru (11/4/2016)

---

Eric M Russell (11/4/2016)

---

Or you could leave the columns as is and add page compression, which in this case would probably shrink the table down to...

sqlfriends (11/7/2016)

---

A further question, if function are not worked efficiently, why T_SQL has this table valued functions?

In which case we should create functions?

I can think of is for calculation, parse,...

Why do you need anything more than a straight-up SELECT statement?

Eric M Russell (11/4/2016)

---

Or you could leave the columns as is and add page compression, which in this case would probably shrink the table down to 10% or less of...

The DATA VALUES are absolutely meaningless in determining if you can drop a column or not!!! You must do a FULL AND COMPLETE impact analysis, searching EVERY piece of code...

KGJ-Dev (11/4/2016)

---

this is what i could think off

Declare @UserGroup nvarchar(MAX);

SET @UserGroup = '|User1|User2|User3^UserGroup2@|user4|user5|user6^Usergroup3@';

selecT case when charindex('|',uc.UserGroup) = 1 then null else uc.UserGroup end, us.Item

FROM dbo.DelimitedSplit8K(@UserGroup,'^') gs

CROSS...

I wonder if there isn't a simpler/more efficient solution if you can introduce a third delimiter thusly (either when the string is built or with a regex, etc):

SET @UserGroup =...

I think Visual Studio (maybe SSDT?) has some capabilities:

https://msdn.microsoft.com/en-us/library/dd172119(v=vs.100).aspx

SQL Cop definitely does:

http://sqlcop.lessthandot.com/