November 10, 2010 at 3:10 am
Great, thanks a lot for the link.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 10, 2010 at 1:06 pm
got it installed, this one does go to 11
November 10, 2010 at 1:08 pm
alen teplitsky (11/10/2010)
got it installed, this one does go to 11
uuuugggggghhhh!! (Funny though)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 10, 2010 at 1:12 pm
November 11, 2010 at 1:35 am
Hello I have also installed the SQL Engine and the SSMS and take some notes on SQL Server 2011 installation
What is interesting is although there was a warning about the upgrade of SSMS, at the end of setup process I have two versions of SSMS 🙂
By the way the new GUI is much more like VS2010
November 11, 2010 at 1:47 am
Also testing at the moment...
can someone try the following please?
create a small db in 2011, set compat mode to 2008, back up, try to restore in 2008, see the unexpected weird error.....
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 11, 2010 at 6:21 am
Henrico Bekker (11/11/2010)
Also testing at the moment...can someone try the following please?
create a small db in 2011, set compat mode to 2008, back up, try to restore in 2008, see the unexpected weird error.....
Backups don't normally restore back versions. Compatibility has to do with coding standards and a few details like that, not with the version number stored in a backup file.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 11, 2010 at 6:29 am
Henrico Bekker (11/11/2010)
create a small db in 2011, set compat mode to 2008, back up, try to restore in 2008, see the unexpected weird error.....
Not expected to work. Has never been possible on any recent edition of SQL.
Each SQL version has an internal database version associated with it. That's stamped into every database's boot page. A database can be restored/attached if it's database version is less or equal to the server's version. If the database's version is higher, the restore attach will fail. Has for 2008-2005, 2005-2000 and as far as I know before that.
If the error isn't clear, that's a bug, but the not restoring is perfectly expected.
The compat level just changes how some aspects of T-SQL are processed and interpretted. It does not change the database's file structure or internal version.
Edit: that reminds me, I have a bug to submit...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 14, 2010 at 10:26 pm
Much hyped....all must have heard about BISM and the roadmap for SSAS and MDX
What happens next?
Raunak J
November 15, 2010 at 1:21 am
GilaMonster (11/11/2010)
Henrico Bekker (11/11/2010)
create a small db in 2011, set compat mode to 2008, back up, try to restore in 2008, see the unexpected weird error.....Not expected to work. Has never been possible on any recent edition of SQL.
Each SQL version has an internal database version associated with it. That's stamped into every database's boot page. A database can be restored/attached if it's database version is less or equal to the server's version. If the database's version is higher, the restore attach will fail. Has for 2008-2005, 2005-2000 and as far as I know before that.
If the error isn't clear, that's a bug, but the not restoring is perfectly expected.
The compat level just changes how some aspects of T-SQL are processed and interpretted. It does not change the database's file structure or internal version.
Edit: that reminds me, I have a bug to submit...
Thanx all, BUT - I know this, my point was:
see the unexpected weird error.....
It doesn't state the obvious old error of version differences.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 29, 2010 at 2:51 am
A warning!
Don't know if anyone else has had this, after I installed it I couldn't run any SSIS 2008 packages with Visual Studio 2008, it said that it was the wrong version, had to restore PC to before I did the install.
I installed it on my PC which I use for work, mainly SSIS and SSMS with 2008 R2 so SSIS still can only use VS 2008. I presume SQL 2011 SSIS now has to use VS 2010 but unlike other duel installs something must have crossed over.
I'll have to try again on a virtual machine.
November 29, 2010 at 3:50 am
Honestly a pre-release version shouldn't be installed on a machine that you care about and are not willing to reinstall completely afterwards. Often the uninstall of the pre-release versions leaves something to be desired.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 29, 2010 at 3:56 am
I know, I shouldn't have done it but couldn't resist, I should have just put it on a virtual straight away.
December 5, 2010 at 12:44 am
Hi,
I just implemented HADR (Availability Groups) in my test virtual Setup.
I used the following Infrastructure To implement HADR / High Availability Group
1) Domain Controller for Authentication
2) Two Virtual Machines with Windows Server 2008 R2 with Failover Clustering installed on each Node.
3) Local Instance of SQL Server (Not Clustered Instance) installed on Virtual Machines with Windows Server 2008 R2 (which are mentioned in point 2)
More Details and Step by Step Guide with screen shots is posted here
Suggest me some good test scenarios to test this HADR (Availability Groups) solution now.
Thanks
DBATAG
Website : http://sqlserver-training.com
Email : dbatag@sqlServer-Training.com
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply