If you can do w/o the direct DupesCount, you can also use an EXISTS check:

SELECT

dm.*

FROM @DuplicateMembers dm

WHERE EXISTS (

SELECT 1

...

I like the technique overall, but the concatenation will likely hurt performance: maybe only slightly, maybe a lot, depending on indexing. Thus, I suggest GROUPing and JOINing w/o any...

For a 500GB db, those are modest amounts of space to be available/reserved.

I think trying to shrink that db would do far more harm than good.

If you have multiple data...

You need to go thru the process of designing tables to store what you need, including a process called "normalization".

Under no circumstances should you attempt to store multiple values in...

Change all filegrowth to fixed amounts rather than %s. That is, change anything like "10%" to a fixed amount instead, such as "1MB".

If you plan to store packages in...

karthik.catchme (1/31/2013)

---

I also found the below lines from "http://support.microsoft.com/kb/315512"

•If you combine the autogrow and autoshrink options, you might create unnecessary overhead. Make sure that the thresholds that trigger the grow...

ben.brugman (1/31/2013)

---

I totally agree that a clustered index will help performance...

FYI, in case you want it, here's the query I use to get an overview of tables, indexes and their sizes:

SELECT

SCHEMA_NAME(o.schema_id) AS Schema_Name,

...

vlad-548036 (1/30/2013)

---

Thanks, that's what I initially had on my system. It is apparent now, that there is no way

declare @howMany int=3

insert top (@howMany)

can be used to force insertion...

First, let's be grateful he's a developer,...

Yes, shrinking log file routinely or unnecessarily is bad.

But A log shrink after an unusually extreme amount of activity would not be.

Yep; I'm sure of that too. 100% homework (or bad interview...

No, no syntax errors per se, but that method's not guaranteed to work safely either.

insert dbo.N

output inserted.$identity into #tmp ( i )

default values

go 3

select *

from #tmp

You may or may not need partitioning.

But you absolutely need to determine the proper clustered index for the table.

It's the column(s) you (almost) always specify in a WHERE clause, particularly...