I would do a query with:

SELECT

COUNT(*) AS [Total],

COUNT(DISTINCT column_1) AS [Column_1],

COUNT(DISTINCT column_2) AS [Column_2],

...

To be safe, I would move everything.

If/as you feel a particular object is not needed, rename it (or move to a different schema/db, if you prefer). See if any...

If you can, for now I'd just move the remaining tables temporarily to another filegroup, completely emptying the original fg, then shrink it. Finally move the remaining tables back...

Did you deletes of lots of table data in some cases rather than table drops?

At any rate, just to be sure, I would run sys.dm_db_index_physical_stats () on remaining tables to...

The setup and maintenance on full-text indexes is not trivial.

It's not a problem for a full-time DBA, but if you're not a DBA, it can be a tricky thing, especially...

I wouldn't automatically add a leading %. That forces a full scan which is often unnecessary if the requestor knows what the first name starts with.

Instead, allow the user...

You should be able to update all rows at once, like so:

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

GO

ALTER TRIGGER [dbo].[tr_TaxID]

ON [dbo].[Item]

after INSERT, UPDATE AS

UPDATE [dbo].[Item]

SET

taxid...

I would just use a CASE statement.

But you raised a good point I overlooked.

If you do need only current year's data, I should have added a WHERE clause with a...

SELECT

name,

SUM(CASE WHEN date_column >= CAST(YEAR(GETDATE()) AS char(4)) + '0101'

THEN total ELSE 0...

Not 100% sure, don't think it's a lot longer. Neither one is very fast really rebuilding 🙂 .

For (almost) pure reads, as O/S and SQL pgms are, RAID5 should be faster than RAID10, with the same number of spindles for each RAID.

So, I'd say use...

An UPDATE statement will always cause some type of lock(s) on the table. SQL must do locks to insure the integrity of the UPDATEs.

Depending on the number of rows...

If I understand correctly:

((COALESCE([prefix]+'-'), '')+right('0000'+COALESCE(convert([varchar],[numeric],(0)), ''),(4)))

is persisted =yes

For XML data, you are very likely better off specifying XML as the data type rather than varchar(max), since SQL optimizes XML storage.

When did SQL Server start doing these "auto sorts" for clus indexes?