Viewing 15 posts - 21,151 through 21,165 (of 22,219 total)
Microsoft will allow you to transfer your Developer license to a Database license. I know because I did it. You just have to remove the developer edition before installing DBPro....
"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 29, 2008 at 10:54 am
Personall, I'd start here.
"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 29, 2008 at 10:50 am
You want to normalize the data as much as you need to. There really isn't a "too far" or a "not far enough." Meet the business requirements in the best...
"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 29, 2008 at 9:13 am
Using cursors at all is frequently a poor choice to solve a problem. However, if you have to use two cursors, use two cursors. Declare both, open both, parse through...
"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 29, 2008 at 9:06 am
Are you kidding? I skip the ones that I know I don't know and I'm still only batting about 58%. Lighten up on yourself just a bit.
"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 29, 2008 at 8:47 am
Great editorial. Thanks for putting it out there.
We're in the early stages of design for a new project and we were honestly counting on a number of features in 2008...
"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 29, 2008 at 6:55 am
It would work for string comparisons though, but a case insensitive database wouldn't need to force the strings to all UPPER case in any regard. It doesn't address 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
January 29, 2008 at 6:48 am
Yeah, I noticed this morning that I didn't have it quite right. I'd joined against the table, but I didn't also provide criteria for the column. Sorry about that. How'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
January 29, 2008 at 6:27 am
I'm not sure why you're getting the collation errors. One of the columns must be marked differently. How about this as a query:
select p.name
...
"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 28, 2008 at 11:01 am
That's elapsed time on the client then. Have you looked at the execution plans?
"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 28, 2008 at 10:50 am
Sorry, I didn't read the whole post (again).
That is odd. Where are you measuring the time elapsed, the server or the client?
Have you looked at the execution plan? Maybe most...
"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 28, 2008 at 8:04 am
Probably because most of the time is spent in martialing the rows of data, not particular columns.
"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 28, 2008 at 7:50 am
The problem with dynamic queries is that they can lead to recompiles and poor plan reuse. While they solve some problems, they can introduce others.
"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 28, 2008 at 7:46 am
Imke Cronje (1/28/2008)
Checked out execution plan and its shows this:
Query Cost (relative to batch) : 100%
Estimated Operator Cost: 99...
"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 28, 2008 at 7:43 am
Basically the case statement is resolving either to 1 or 0. If it's 1, then 1=1 at the end of the case statement. If it's zero, then 0 certainly does...
"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 28, 2008 at 6:06 am
Viewing 15 posts - 21,151 through 21,165 (of 22,219 total)