Viewing 15 posts - 6,391 through 6,405 (of 22,219 total)
Not a problem. Happy to help. You know where to go if you have questions.
"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
April 9, 2015 at 12:04 pm
sqlfriends (4/9/2015)
This table has no...
"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
April 9, 2015 at 10:57 am
I'd suggest more direct control. Write a statement at the beginning that explicitly creates the table using the structure and name you want and then INSERT...SELECT instead of SELECT...INTO.
"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
April 9, 2015 at 10:49 am
Only if it's supplied through the connection string. Which, effectively, means no.
"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
April 9, 2015 at 10:48 am
Why not use GETDATE, or better still, GETUTCDATE, to retrieve the date and time you're doing your edits. You don't need to manually modify a 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
April 9, 2015 at 10:47 am
You mean this book?
Like Gail says, to SQL Server, there's no difference between a client side timeout and you just killing a query that's running in SSMS. Neither one generates...
"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
April 9, 2015 at 10:45 am
tcronin 95651 (4/9/2015)
"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
April 9, 2015 at 8:46 am
Jeff Moden (4/9/2015)
Grant Fritchey (4/9/2015)
Check Database IntegrityDatabase Backups
Log Backups
Backup Testing
Statistics Maintenance
Index Maintenance
Those are the basics I think.
Just to add to that fine list... Checks on performance and resource usage (usually...
"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
April 9, 2015 at 8:45 am
Adding INCLUDE columns to a nonclustered index doesn't affect the clustered index, it's use or maintenance. They only affect the nonclustered indexes.
"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
April 9, 2015 at 7:10 am
And here's the problem with NULL values. An absolute unknown can't equal an absolute unknown. Also, running functions on both columns like that will absolutely destroy performance. I'd strongly suggest...
"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
April 9, 2015 at 7:09 am
You'll restore the logs using STOPAT. This is a little older, but it's still a good article on how to do a point in time restore[/url]. I have an article...
"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
April 9, 2015 at 5:11 am
Plus, it's evaluation, test it. Worst thing happens, you need to set it up again. It's not your production server.
"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
April 9, 2015 at 5:09 am
Start with the backups, as you've already done. But, talk to the business about Recovery Point Objectives and Recovery Time Objectives to ensure your backups meet those requirements. Also, make...
"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
April 9, 2015 at 5:08 am
Check Database Integrity
Database Backups
Log Backups
Backup Testing
Statistics Maintenance
Index Maintenance
Those are the basics I think.
"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
April 9, 2015 at 5:04 am
Fill factor is a matter of experimentation, not size. If it's fragmenting fast, you might want to set it to 70 and see how that goes. Just remember, the smaller...
"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
April 9, 2015 at 4:33 am
Viewing 15 posts - 6,391 through 6,405 (of 22,219 total)