You should have a clustered index. The storage engine is built around tables having clustered indexes.

Unless you're doing millions of single-row inserts per second, you're unlikely to hit problems...

g.britton (11/13/2014)

---

SeanNerd (11/13/2014)

---

My question is about indexing strategy for the following scenario:

I have a table where we cannot use the typical int identity primary key column. The table can have...

Do you know what O(1) means?

And you're absolutely sure that there's no chance they can be used by a business process that...

rodjkidd (11/13/2014)

---

Jack Corbett (11/13/2014)

---

Wow, the thread has been quiet lately.

Had a great time at the PASS Summit last week where I got to see many threadizens....

Why are you partitioning it? What is the goal?

What was the command?

Order of parameters in a where clause does not matter

Why do you think they don't support full backup (which I assume means full database backup)?

Generate the ALTER scripts for the procs and add WITH ENCRYPTION. No real easy way.

Bear in mind that it's not actually encryption and it takes someone who knows what they're...

Don't name the constraint. Unlike temp table names, constraint names aren't 'uniqified', so by naming it you're ensuring that it is impossible for two sessions to run that proc at...

You can never rebuild to fix...

Index 1 = clustered index = actual data loss. Restore from last good backup + log backups.

Beautiful. Ok, 4 NUMA nodes, each with 8 physical cores. Try maxdop at 12 to start, 8 and 16 also viable values.

Before you make assumptions about what apps are a...

5. Move the data files to faster drives (permanently)

6. Put the...