Viewing 15 posts - 7,516 through 7,530 (of 22,219 total)
Sean Lange (9/3/2014)
Gazareth (9/3/2014)
Koen Verbeeck (9/3/2014)
xsevensinzx (9/3/2014)
"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
September 3, 2014 at 9:02 am
HowardW (9/3/2014)
Grant Fritchey (9/3/2014)
"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
September 3, 2014 at 8:34 am
Core problem there is that you may not know what you don't know, meaning, it's entirely possible for there to be queries coming from sources that you don't know that...
"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
September 3, 2014 at 7:39 am
I'd simply set up a test to show it. Create a copy of your tables and show queries with and without Column C. Specifically, focus on the execution plan to...
"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
September 3, 2014 at 7:09 am
Pretty much that whole WHERE clause is an issue. Functions on columns or functions to determine values within a WHERE clause, JOIN criteria or a HAVING clause will all impact...
"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
September 3, 2014 at 7:06 am
Adding a new table, no. If we're just talking about adding a blank table to the database and nothing else.
Adding that column to a table, well, it depends. If it's...
"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
September 3, 2014 at 4:01 am
There are also a number of limits on data types. There are no foreign keys supported. Not all T-SQL statements are supported. It's a very specialized set of functionality.
"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
September 3, 2014 at 3:40 am
You should run the SQL Server 2014 Upgrade Advisor.
"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
September 2, 2014 at 3:41 pm
The basic approach is to record the behavior of your queries in 2008. Get the execution times, resources used, and, for really interesting queries, the execution plan. Then do the...
"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
September 2, 2014 at 10:30 am
The page latches could be from slow disk, or memory issues, or stuff like that, sure. But, it could also be from scans where seeks would work better because bad...
"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
August 31, 2014 at 1:13 pm
No certifications at all and my salary is more than adequate. I also seriously doubt I would be paid more if I had an MCSE or almost any other cert...
"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
August 27, 2014 at 5:00 pm
Kulgan_ (8/27/2014)
In addition... when You do the "select *" DB still have to grab all the data from disk... If columnstore index would include all columns then in theory this...
"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
August 27, 2014 at 5:24 am
ChrisM@Work (8/26/2014)
Grant Fritchey (8/26/2014)
"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
August 26, 2014 at 10:38 am
You can't do this through the backup and restore process, no. You'd have to build some type of data migration. That's possible, just a lot of work.
"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
August 26, 2014 at 4:30 am
Nice Chris, you took away my two comments, on the RIGHT JOIN getting turned into an INNER JOIN and that awful string manipulation against a column. Those were my two...
"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
August 26, 2014 at 4:29 am
Viewing 15 posts - 7,516 through 7,530 (of 22,219 total)