Viewing 15 posts - 21,346 through 21,360 (of 22,219 total)
Instead of what you had:
SELECT DISTINCT Address1, Address2, City, Postcode, COUNT(Postcode)
FROM AddressTable
GROUP BY Postcode
HAVING COUNT(Postcode)
Why not simply do this?
SELECT Address1,Address2,City,PostCode,Count(PostCode)
FROM AddressTable
GROUP BY Address1,Address2,City,PostCode
HAVING Count(PostCode) > 1
The GROUP...
"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 4, 2008 at 5:43 am
It has to be permissions. Just what it says. Remember, the backup is not running as you, it's running as the account that SQL Server runs under. So you have...
"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 4, 2008 at 5:33 am
OK. That is odd then. I use this function regularly and it doesn't bump tempdb up to 20gb (I'd notice). Any triggers or anything like that on the table 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
January 3, 2008 at 1:00 pm
It doesn't surprise me to see it in the tables with 50 rows. I ran into the same issue with tables that had less than ~200 rows.
The others... I'm not...
"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 3, 2008 at 12:59 pm
You can do this through Management Studio very quickly. Right clicking the object brings up a menu with "Script Stored Procedure as" and then another menu that has choices like...
"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 3, 2008 at 12:54 pm
We use that all the time with no serious issues. But then I've never monitored tempdb while running it. Are you breaking up your trace files or creating one gigantic...
"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 3, 2008 at 12:49 pm
How many rows are in the tables? I've seen this when the number of rows is very low. Other than that, rebuilding the index usually changes the fragmentation percentage.
"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 3, 2008 at 12:25 pm
So, would it be plagiarism to copy that from you?
"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 3, 2008 at 12:09 pm
At this point in time, keep your plans to work with 2000, but go ahead & skip 2005 and start learning 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 3, 2008 at 11:39 am
Take a look at the catalog views. Sys.Tables & Sys.Data_Spaces. This is quick & dirty:
select t.name as TableName
,s.name as FileGroupName
from sys.tables t
join sys.data_spaces s
on s.data_space_id = t.lob_data_space_id
"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 3, 2008 at 11:37 am
I found a blog entry over at MSDN that talks about this:
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
If you scroll down to Message #10:
Reason:
1) There are spaces after Instance name in 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 3, 2008 at 10:44 am
I think you have something else going on. The delays are not normal.
"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 3, 2008 at 10:41 am
Well it's about time.
Congratulations Steve! You earned it.
"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 3, 2008 at 5:51 am
Hey Jeff,
Do you have that response in a script so you can just point & click? If so, can you share the script?
"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 3, 2008 at 5:50 am
Hi Sandy,
When you run backups, don't use drive paths like this:
BACKUP DATABASE x TO DISK = 'C:\x.bak'
Because it will place them on the relative drive for that server. Instead,...
"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 3, 2008 at 5:47 am
Viewing 15 posts - 21,346 through 21,360 (of 22,219 total)