Viewing 15 posts - 18,796 through 18,810 (of 22,219 total)
Jack Corbett (1/9/2009)
"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 9, 2009 at 8:02 am
RBarryYoung (1/9/2009)
I've done this before and been quite happy with it. What do you find the problems to be, Grant?
My primary problem with it is maintenance. It becomes extremely...
"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 9, 2009 at 7:50 am
GilaMonster (1/9/2009)
Grant Fritchey (1/9/2009)
There's about 3 inches of completely frozen snow in my yard and another 4-6 inches of the fluffy crap on the way tomorrow night.BLECH!
It's been 30+ degrees...
"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 9, 2009 at 7:45 am
I don't know your location or training budget, but I'd be remiss if I didn't suggest looking into Andy Warren and his team down in FL at End2End training. Great...
"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 9, 2009 at 7:43 am
See, my memory stinks. It's Massively Unified Code Keys (MUCK) tables.
The first article:
http://www.sqlservercentral.com/articles/Advanced/lookuptablemadness/1464/%5B/url%5D
Here's a great discussion about the topic too. One True Lookup Table is another name for the design:
http://www.sqlservercentral.com/Forums/Topic154165-204-1.aspx
Suffice...
"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 9, 2009 at 6:52 am
blandry (1/9/2009)
"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 9, 2009 at 6:45 am
Domagoj Orec (1/9/2009)
Hi all.I just wanted to be part of this thread, 63 pages and I've just entered it today :w00t: :alien:
See you in February after you finish reading everything.
"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 9, 2009 at 6:42 am
Yeah, that's a winner.
"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 9, 2009 at 6:42 am
Your initial table definition:
userid (uniqueidentifier)
username (nvarchar)
points (int)
plays (int)
comments (int)
The query giving you problems:
UPDATE UserStats SET TotalPlays=TotalPlays + 1 WHERE Username=@username
Where is the column TotalPlays coming from? It's not there.
I...
"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 9, 2009 at 6:38 am
There's a whole section on identifying gaps in Itzik Ben-Gan's book T-SQL Querying. Here's a way to list all the gaps, their start points and stop points:
SELECT cur+1 AS start_range,...
"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 9, 2009 at 6:32 am
I'm confused as to why BULK INSERT is not generating the correct data. It's generally going to work better than straight inserts just because of the difference in logging....
"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 9, 2009 at 6:26 am
As to licensing, sure you can run SQL Server on a workstation and have multiple connections. No issues. Well, except for whatever limitations you might run into in terms of...
"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 9, 2009 at 6:22 am
I cannot vouch for the wealth of the selection, but I know that the following places have SQL Server PDF books for sale:
"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 9, 2009 at 6:17 am
I've done both and I have to say, having 100 seperate pick lists is easier, more functional, easier to maintain, easier to document and easier for others to understand, support...
"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 9, 2009 at 6:06 am
I've had to do that, or run the script from the directory where I want to store/read all the files. I'm not that aware of any other choices either.
Adding 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 9, 2009 at 6:03 am
Viewing 15 posts - 18,796 through 18,810 (of 22,219 total)