cfr "don't need to understand code in a object oniented programming language, just use it"

You'll still need to desing your objects, but in the cloud, you shouldn't need to worry...

Keep in mind with a trigger you can use the "inserted" and/or "deleted" objects !

You could just store that info in an audit or logging table an work it out...

With that kind of messages, I would first run a

DBCC CHECKDB

It checks the allocation and structural integrity of all the objects in the specified database.

DBCC CHECKDB ( 'database_name'...

We always perform full maintenance after any migration.

i.e.

rebuild all indexes (explicit)

exec sp_updatestats or UPDATE STATISTICS table / view WITH FULLSCAN

dbcc updateusage(0) with count_rows

Jeff's advise is indeed the best starting place.

Clustering (a/a - A/p) can be used to host clustered sqlinstances.

Load balancing isn't in scope for sqlserver yet ( I didn't check this...

I would suspect your connection isolation level to be more intrusive than the one SSMSexp uses (read committed).

What isolation level are you using ?

Indeed with 64 bit you should always set the max memory configuration or it may actually eat up all your physical ram.

IF you want to get control of processor %...

Great! You figured it out yourself AND posted the valuable feedback.

Happy holidays

With SQL2005 and higher, simply use the OUTPUT clause to be 100% sure of the value assigned to your row(s).

There are a number of articles at SSC regarding the identity...

AFAIK If the current sqlserver would have distributed databases to support your load balancing, only a single one would be in read-write state, the others would be in read-only mode...

did you try this ?

SELECT index_id

, name AS index_name

, STATS_DATE(OBJECT_ID, index_id) AS statistics_update_date

FROM sys.indexes

-- WHERE OBJECT_ID = OBJECT_ID('dbo.Objects')

order by Index_id;

did you restore that database ?

if yes, then check the database owner and put it back to the one it was before the restore (if you didn't alter it,...

If you are considering READ_COMMITTED_SNAPSHOT first check out the impact of its usage ( tempdb ) !

If you have a single Insert/update/delete window, maybe putting the db in read_only mode...

Thank you for the feedback.

It does indeed ring a bell, but far far away 😉

I wouldn't do that, you'll end up having way to much similar indexes !

You need to...