SQL Server 2008 Express RCO

The SQL Server 2008 Express products are Ready, Willing and Able.

http://blogs.msdn.com/sqlexpress/archive/2008/06/10/sql-server-2008-express-rc0.aspx

I just installed the (FREE) Advanced Features version on XP Pro SP3.

The biggest addition for DASP Developers is the new Import and Export features.
You can now Import and Export to and from local and remote SQL Servers.

Notes:

On XP you have to be running the .NET 3.5 Framework SP1, or later.
The first FX version for XP will not allow this to install, you need this version:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8c36aca4-e947-4760-9b05-93cac04c6f87

You also need to have Windows Installer 4.5 and PowerShell 1.0

At least two reboots will be required on XP.

I'm already running SQL Server 2005 and SQL Server 2008 on my Vista box so I've only tested 2008 Express on XP.
Salute,
Mark

 

Updated:
http://blogcastrepository.com/blogs/wisemx/archive/2008/06/12/sql-server-2008-express-rc0.aspx

Added notes from the Microsoft SQL Express Team

 

I just loaded SQL 2008 Standard on Vista, and it runs fine on my local machine. However, when I try to reach my SQL 2005 account here, I get the error:


TITLE: Microsoft SQL Server Management Studio
------------------------------


Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)


For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476


------------------------------
ADDITIONAL INFORMATION:


An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


------------------------------


The server principal "SQL2005_504266_mockler_user" is not able to access the database "SQL2005_468370_evention1" under the current security context. (Microsoft SQL Server, Error: 916)


For help, click: http://go.microsoft.com/fwlink?Prod...rc=MSSQLServer&EvtID=916&LinkId=20476


------------------------------
BUTTONS:


OK
------------------------------



Any idea on how I can connect 2008 to a SQL account here? (I can connect fine here with my Management Studio 2005.)
Thanks,

Paolo

 

Thanks bro, I am indeed a father of three young children, with my lovely Brasilian wife Leticia.
(Samuel, Gabriela and Lucas)
http://blogcastrepository.com/photos/marks_shots/default.aspx

Yes the connection methods are the same but SQL Server 2008 is very full of new feartures.

I'm tracking all known SQL Server 2008 issues each day and will keep every posted.
Saltue,
Mark

 

That's strange, I'm able to connect to SQL Server 2005 from my Vista SQL Server 2008 just fine.
I'll do some checks for ya however.
Salute,
Mark

 

Thank you very much for the help, however, the behaviour is still the same. THe strange thing is that "SQL2005_468370_evention1" is a real account on that server. The same situation for the other remote SQL 2005 server, somehow SQL 2008 management studio is trying to access a different database, not the one I logged in for. Mucho wierdo!


For you, you just connect to the New Sql engine the way you did in 2005, right?


Happy Father's day, if you are a father,





Paolo

 

I am having this exact issue - has anyone found a fix?
***************************
Hi,
</o>
I am running into an issue that I really need resolved today. Simply put, I am getting the error:
</o>
The server principal "dhtest" is not able to access the database "dhtest2" under the current security context. (Microsoft SQL Server, Error: 916)
</o>
But, the details are a little fuzzy...
</o>
I have two installations of SQL Server 2008 RC0.
</o>
Microsoft SQL Server 2008 (CTP) Enterprise Edition (64-bit) CTP is installed on one server running Windows Server 2008 x64.
And, Microsoft SQL Server 2008 (CTP) Enterprise Edition CTP is installed on the other server running Windows Server 2003.
</o>
Both were installed with the same installation options (the SQL services are all running using a local admin account).
</o>
I created two databases on the x64 server:
</o>
db: dhtest
user: dhtest with dbo permission dhtest
</o>
db: dhtest2
user: dhtest2 with dbo permissions to dhtest2
</o>
I then try connecting via sql server management studio using SQL authentication and get this error:
</o>
The server principal "dhtest" is not able to access the database "dhtest2" under the current security context. (Microsoft SQL Server, Error: 916)
</o>
But . . . I can connect to the x64 server from the server running Windows Server 2003 with SQL server management studio just fine. No errors at all and I have access to the assigned database as expected.
</o>
I also tested connecting from the x64 server to the Windows server 2003 with sql management studio and got the same error.
</o>
So... it appears to be a security setting on the x64 box.
</o>
In event viewer I see the errors below but it doesn't make sense because the Windows Firewall is turned off.
</o>
The Windows Filtering Platform has blocked a bind to a local port. Application Name: \device\harddiskvolume1\windows\system32\svchost.exe
Network Information:
Source Address: 0.0.0.0
Source Port: 59535
Protocol: 17
*********************
Process ID: 240
Application Name: \device\harddiskvolume2\program files (x86)\microsoft sql server\100\tools\binn\vsshell\common7\ide\ssms.exe
If anyone has any suggestions at all, I would greatly appreciate it.
</o>
Desiree

 

Hi,
Did you try pinning the SQL Server shortcut then changing the shortcut to run as Admin?
Salute,
Mark

 

Hi,

Thank you for your response, but that didn't work. I selected to run as administrator, but then I connect using SQL authentication (as this is how our users will connect) and it fails with the same error. Any other ideas?


Desiree

 

Hi,
I just checked the known issues via my Microsoft Connect account and all of them were the same.
This error was corrected by running the local services at Administrator, even on x64 systems.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=198005&amp;wa=wsignin1.0

Other than that I don't have anything for you at this time.
Salute,
Mark

 

Hello,





I can not reach the link mentioned,
This error was corrected by running the local services at Administrator, even on x64 systems.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=198005&amp;wa=wsignin1.0

Could you post a new link, if there is one?

Would this mean that a user of SQL 2008 can not use a shared SQL Server,the way many of us do who do not have a dedicated Web servers and SQLservers (or who can not control all aspect of a SQL box)?

Thanks,

Paolo

 

Hi,
I'll paste the info from the Msft Connect page:

Note that the Microsoft rep stated that not only are the Administrator privileges needed but also the user account.
As an example on my Vista system with Admin rights I login as speedy\wisemx
If I try to login with just the instance name it will fail. ("speedy" is mySQL Server instance, "wisemx" is the Admin, me.)
Salute,
Mark