Viewing 15 posts - 2,926 through 2,940 (of 22,219 total)
Well... to a degree this is true. In terms of storage and retrieval, 40 characters in a NVARCHAR(40) or in NVARCHAR(4000) or even in NVARCHAR(MAX) will perform the same way....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
All those SELECT statements used to put the data together could potentially be tuned. I'd check each of the execution plans to see what's happening. Also this: "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
Reinforcing Thomas' answer. Backup every database on the server (except tempdb) and you've backed up the server. All the logins, etc., are stored in system databases. Capture those, you've captured...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
I've generally used two approaches. First, Distributed Replay is free with SQL Server. It will let you replay a captured set of events (trace or extended events) against...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 15 posts - 2,926 through 2,940 (of 22,219 total)