Viewing 15 posts - 5,191 through 5,205 (of 22,219 total)
salardx (1/21/2016)
We CANNOT have much indexes in the tables (neither one table for each month, nor 10,000 tables!)
because data is bulking into the tables! 1000 records on each bulk!...
"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
January 21, 2016 at 5:33 am
Please, please, please, I already feel like I've been picking on this person, so no piling on. But they're looking for help and I don't think I'm providing it in...
"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
January 21, 2016 at 5:09 am
salardx (1/21/2016)
Do any of the files that you load have the same structure? If so, why not put them into the same table? And why create a new database each...
"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
January 21, 2016 at 5:07 am
The very best way to deal with scale is start with the fundamentals. Making good choices on the clustered index, primary key (not the same things), unique constraints, normalization, data...
"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
January 21, 2016 at 4:02 am
I don't understand what you're going for. When you say you want to "check five columns uniqueness by checking one column" you're stepping outside of standard mechanisms.
What I'm suggestion is...
"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
January 21, 2016 at 3:22 am
There are lots of ways to document a procedure. It really depends on why you're documenting it, for what purpose, for what audience.
One option is to look to a third...
"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
January 21, 2016 at 2:25 am
bebe022476 (1/20/2016)
Here it is:
DocumentID(PK,int,not null)
DocFolderID(int,null)
PublishToWeb(bit,null)
Filename(varchar(100),null)
Filesize(int,null)
ModifiedDate(datetime,null)
TableName(varchar(40),null)
EntityCode(varchar(12),null)
I'm not sure how to attached the jpg screenshot here but the execution plan only has 100% Clustered Index Scan(Clustered) on [document],[pk_document] .
The job normally...
"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
January 21, 2016 at 2:22 am
What about just using a unique constraint?
"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
January 21, 2016 at 2:20 am
For the most part, when it comes to parallelism, your MAXDOP is not the issue. Instead, the issue is almost always around the Cost Threshold for Parallelism. The default value...
"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
January 21, 2016 at 2:19 am
You need to capture the execution plan when the query is performing well and when the query is performing badly. Compare the two plans. There differences should indicate why you're...
"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
January 21, 2016 at 2:16 am
craig-962225 (1/21/2016)
"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
January 21, 2016 at 2:10 am
Lynn Pettis (1/20/2016)
Grant Fritchey (1/20/2016)
"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
January 20, 2016 at 10:25 am
Sitting in a meeting at Redgate talking about plans for SQL Server Central. THE THREAD has come up as a topic. We are currently a 65mb thread. It evidently looks...
"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
January 20, 2016 at 8:55 am
COPY_ONLY will only affect differential backups, not log backups. Log backups can be associated with any full backup, even ones that have been taken using COPY_ONLY. It's only when you...
"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
January 20, 2016 at 3:00 am
I am prejudiced, but Redgate SQL Backup is a great piece of software (I work for them).
You might also want to look at Minion Backup.
"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
January 20, 2016 at 2:57 am
Viewing 15 posts - 5,191 through 5,205 (of 22,219 total)