Viewing 15 posts - 12,226 through 12,240 (of 39,804 total)
Anything more you can tell us? Providing more information might allow someone here to help you.
June 26, 2013 at 10:24 am
You have
move to e
It should be
move to e:\
June 25, 2013 at 6:16 pm
IMHO (6/25/2013)
June 25, 2013 at 7:58 am
Just so the rest of you can feel jealous, I got a hug from Gail and a handshake from Rodney last week 🙂
June 24, 2013 at 2:24 pm
I'm sure someone will. Feel free to start a FF2013 thread.
June 24, 2013 at 9:45 am
That's not true.
First, upgradation isn't an English word. It's merely an upgrade, or upgrading to SQL Server 2008.
Second, upgrades from SQL Server 2000 or SQL Server 2008 are supported to...
June 20, 2013 at 11:46 pm
wolfkillj (6/20/2013)
June 20, 2013 at 2:01 pm
Happy to help, but we don't like to do homework, tests, or work work for you. Make an attempt.
You haven't really explained how the data should be joined, or...
June 20, 2013 at 7:08 am
Run the upgrade advisor.
There's no simple/easy way to answer this. There can be issues, or the upgrade may go fine.
I'd recommend side by side upgrade rather than in place, but...
June 20, 2013 at 7:06 am
+1 to what Gail said.
It's possible it corrupted during a copy, but that doesn't mean your copies are always going to do this.
June 20, 2013 at 6:47 am
I don't love the save definition, because it doesn't include fielding.
However, it's not the runs later are more important, but the situation changes and it is harder to perform in...
June 20, 2013 at 6:41 am
I don't think this works natively.
Red Gate software makes a tool (SQL Source Control) that does this.
http://www.red-gate.com/products/sql-development/sql-source-control/
Disclosure, I work for Red Gate.
June 20, 2013 at 6:28 am
+1 to what Howard wrote.
June 20, 2013 at 6:27 am
Errors 823/824/825 will be raised.
If you suspect corruption, run DBCC CHECKDB.
June 20, 2013 at 6:26 am
calvo (6/19/2013)
June 20, 2013 at 6:13 am
Viewing 15 posts - 12,226 through 12,240 (of 39,804 total)