Viewing 15 posts - 19,381 through 19,395 (of 22,213 total)
Funny, I was wondering the same thing. I even did a google search to try to track it down.
October 24, 2008 at 7:00 am
Backups, absolutely.
And, this one does make people crazy, but I've been insisting on it for over a decade now... a tested script to deploy changes to production. No winging it,...
October 24, 2008 at 6:06 am
The issue I'm seeing is that Nested Loop operator, NodeId = 17, right before the Hash Match, NodeId = 16, that's performing the aggregation. Two issues there, first, it's using...
October 23, 2008 at 10:53 am
Buck Woody addressed this question in a recent blog post:
http://blogs.msdn.com/buckwoody/archive/2008/10/20/erd-designer.aspx
October 23, 2008 at 7:11 am
I got that link from our local Microsoft rep. I'm assuming it's on the RSN schedule (Real Soon Now).
October 23, 2008 at 7:09 am
If you don't have a clustered index on the table, I'd at least put one on that ID column. After that, take a look at the execution plans to determine...
October 23, 2008 at 6:38 am
There are exceptions, but by and large, every table should have a clustered index. The nonclustered indexes have to use RID to track down the data, which is generally not...
October 23, 2008 at 6:33 am
I'm not aware of a resource for making these types of decisions except for common sense and experience. You could go to a consulting firm or bounce the ideas off...
October 23, 2008 at 6:25 am
What about the Dudettes?
Anyway, short of installing it & checking the version, I'm not sure what you could do.
October 23, 2008 at 6:14 am
And while I'm on it, I've run Powershell scripts against SQL Server 2008 before. I created a silly little test script for placing a load on a copy of AdventureWorks...
October 22, 2008 at 8:48 am
It looks like it did precisely what you told it to. It limited the names to where they did not equal 'Name1' and it showed those for values not...
October 22, 2008 at 8:21 am
Or
SELECT f.footballer_name
,a.goals_scored
FROM football.table f
JOIN another.table a
ON f.footballer_name = a.footballer_name
WHERE f.mins_played > 300
The problem you defined is a classic and simple JOIN between two tables.
October 22, 2008 at 6:25 am
It's just a scan against a heap? You won't see any real improvements there until you change the situation, adding a clustered index, or an index, period. 7.0 might just...
October 22, 2008 at 6:01 am
Nothing free that I'm aware of. SQL Prompt is pretty inexpensive though. It's got a real return on investment with the speed you can realize in writing TSQL code. You...
October 22, 2008 at 5:55 am
In general, there are exceptions, you should have a clustered index on each table. You only get one and it affects how the data is stored, not just how it's...
October 22, 2008 at 5:53 am
Viewing 15 posts - 19,381 through 19,395 (of 22,213 total)