Viewing 15 posts - 12,121 through 12,135 (of 22,214 total)
SQLRNNR (8/8/2011)
GilaMonster (8/8/2011)
Ask Grant about GoDaddy, and take a couple steps back.
Grant didn't like it at all, but I also believe his configuration was a bit different than what they...
August 8, 2011 at 11:47 am
GilaMonster (8/8/2011)
Ask Grant about GoDaddy, and take a couple steps back.
He should take a couple of steps back, then ask about GoDaddy.
Short answer, no, I don't think much of them....
August 8, 2011 at 11:44 am
I don't have a good tutorial for you on doing this upgrade for replication. By & large, upgrades are better and safer when they're done as a side-by-side upgrade, meaning...
August 8, 2011 at 11:00 am
Also, depending on how the jobs are configured, you might have a single job doing things for multiple databases. Just to be aware in case whatever search mechanism you put...
August 8, 2011 at 7:42 am
right there with you too, bu what generated the error? Go there first. I don't know, there's got to be more to this question than first appears.
August 8, 2011 at 6:35 am
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...
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....
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.
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.
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...
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.
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...
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...
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.
August 5, 2011 at 8:35 am
Viewing 15 posts - 12,121 through 12,135 (of 22,214 total)