Viewing 15 posts - 12,136 through 12,150 (of 22,224 total)
Have to add this: Why is my log full.[/url]
"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
August 8, 2011 at 6:29 am
Just so you know, SQL Compare from Red Gate Software[/url], can even compare a live database to a backup file. You don't even have to restore the database to make...
"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
August 8, 2011 at 6:16 am
I'm sure I'm missing something, but it looks like you're trying to use @@IDENTITY with a uniqueidentifier data type. They're not the same and that would explain the fundamental issue....
"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
August 8, 2011 at 6:13 am
Maybe I'm a little slow, but remove the old server from your backup process. Unless there's something here you're not stating, that seems to be the answer.
"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
August 8, 2011 at 6:10 am
SQL Dev-938873 (8/7/2011)
Thanks for ur replies..Can plz suggest... which is better from SQL Server or From Front End (.Net)????
A couple of us have said it. The front end.
"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
August 8, 2011 at 5:53 am
GilaMonster (8/6/2011)
Grant Fritchey (8/6/2011)
In SQL Server 2008 and greater, you could use DATETIME2 data type which can also manage time zones.DateTimeOffset, not DateTime2.
Doesn't handle daylight saving though.
Oh crud. 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
August 6, 2011 at 5:02 am
In SQL Server 2005, you should handle this on the client side. In SQL Server 2008 and greater, you could use DATETIME2 data type which can also manage time zones.
"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
August 6, 2011 at 4:54 am
You're doing the JOIN incorrectly. See, each of those columns is to be joined to the Time dimension individually. If you look at the data, it will make more sense:
ProductKey...
"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
August 6, 2011 at 4:51 am
GilaMonster (8/6/2011)
Ninja's_RGR'us (8/6/2011)
Was it you Gail that said you don't even make 1$ / hour on your articles (this site pays 25$ / article)?
Wasn't me, but it's very true. What...
"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
August 6, 2011 at 4:36 am
Shabba (8/5/2011)
There I was just reviewing your Performance Tuning Video from SQL in the City!By the way thanks for the informative presentation.
Thank you! I hope it's useful.
"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
August 5, 2011 at 8:35 am
It really depends on what you need. For straight forward monitoring and alerting, I suggest my companies software, Red Gate SQL Monitor[/url].
If you want to get into specific query tuning,...
"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
August 5, 2011 at 8:23 am
Microsoft provides a runtime that can be deployed. Search on MSDN. It's there.
"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
August 5, 2011 at 6:00 am
I'm with Gail on this one. Fixed values are much better. You always know exactly how much will be added and you can anticipate the additional load that will place...
"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
August 5, 2011 at 4:57 am
Nope. Especially not a unique index. If it's unique, it's unique. If someone types Heme, Hem or Ham, they're all going into the database.
"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
August 4, 2011 at 3:14 pm
I have to ask, why no backups?
"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
August 4, 2011 at 3:13 pm
Viewing 15 posts - 12,136 through 12,150 (of 22,224 total)