Viewing 15 posts - 21,061 through 21,075 (of 22,219 total)
I provided a link in the post above to MS's tool. Here it is exposed.
"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
February 13, 2008 at 5:34 am
You really don't need to contact MS. The answer is 99. Matt Miller has not only documented it, he's tested it to confirm. 99 is as high as you can...
"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
February 12, 2008 at 6:42 pm
Check the logs. If you had six, you should have seven now. Cycling the error logs simply stops the logging in one log and starts it in the next, new...
"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
February 12, 2008 at 1:23 pm
Why on earth would you need more than 99 error logs? Actually, why would you need more than ten?
The thing I suggested would just show you if you had more...
"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
February 12, 2008 at 1:10 pm
Itzik Ben Gan from Solid Quality Mentors. He wrote the book, literally.
"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
February 12, 2008 at 12:49 pm
Cycle the error log:
EXEC sp_cycle_errorlog;
"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
February 12, 2008 at 12:47 pm
It's not like date fields where there are a lot of special functions. We just use decimal.
"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
February 12, 2008 at 10:37 am
It depends (I love that answer). To me, this is a business definition. Strictly looking at data, as data, no, none of these columns help to define the Address object....
"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
February 12, 2008 at 5:30 am
Absolutely true.
You also might want to look at having simply an Address table with a join table to associate addresses to contacts. That way when you get a married couple...
"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
February 11, 2008 at 10:17 am
The first four of those columns you're talking about are there for auditing purposes and shouldn't have anything to do with relational integrity. The last column, the guid, I'm assuming...
"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
February 11, 2008 at 9:36 am
Since you're not, in any way relating the data between these tables, an odd thing, you could do something like this:
SELECT 'TableA' AS TableName
,Cola AS FirstColumn
FROM dbo.TableA
UNION ALL
SELECT 'TableB' AS...
"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
February 11, 2008 at 9:32 am
If you have to use dynamic sql, be sure to look up & understand sp_executesql as the preferred method of calling it rather than using exec 'somestring'
"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
February 11, 2008 at 8:36 am
I'd have to go all the way to "stupid practices." If I was feeling kind, I might call it "ignorant practices." If I wasn't feeling kind, it'd be "f'ing stupid...
"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
February 11, 2008 at 8:26 am
I find that I'm with the you need both an artificial key and a natural key camp. Usually, but not always, the artificial key is an identity. However, I also...
"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
February 11, 2008 at 7:07 am
tymberwyld (2/10/2008)
Grant Fritchey (2/7/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
February 11, 2008 at 6:25 am
Viewing 15 posts - 21,061 through 21,075 (of 22,219 total)