I installed VS2012, SSME 2012 with localdb, and I discovered that I have 2 servers that I can connect to: (localDB)\v11.0 and (localDB)\Projects.
Which of them do I have to use for execising, what are them both for?
I know I am bit late. But I am facing the same question now and found the answer. Thought I should share the Answer:
(localdb)\Projects is the SQL Server Express LocalDB instance which is used by SQL Server Data Tools by default to host the sandbox databases created for your database projects (*.sqlproj) to enable F5 deployment and debugging.
(localdb)\v11.0 is the generic SQL Server Express LocalDb instance which gets created when LocalDB is installed, and this is also used by other Visual Studio projects like the ASP.NET projects.
See http://msdn.microsoft.com/en-us/library/hh510202.aspx for more information on LocalDB
Update
Starting from EntityFramework 5.0, the default sql server is the your localdb\vxx.x instance now.
This explains the difference and some issues to watch out for
http://aeronaught.wordpress.com/2012/11/22/vs2012-localdb-v11-1-v11-0-automatic-instance-horror/
Not sure on the difference but you should be using
(localdb)\v11.0
Related
So I have a suite of SSIS packages that we created using Visual Studio 2008 and are currently deployed on a SQL Server 2008R2 instance. However, I would like to upgrade these to 2012 via SQL Server Data Tools for Visual Studio 2012 which is easy enough, however, the company that I work for does not have any plans to upgrade the SQL Server to 2012 any time soon. So is there a way to create SSIS packages using SSIS 2012 and deploy them to a SQL Server 2008R2 instance while maintaining all of the new features of the SSIS 2012 package. IE Project Connection Managers and Package Parameters, etc...
Unfortunately, no. The Integration Services Service, the engine that which makes the package go, would have to be installed on the machine to be able to interpret/run them. Furthermore, unless you planned on running the packages from their .ispac containers, you wouldn't be able to take advantage of the rest of the "goodies" like the Environments, at least not without writing some ugly exec calls.
Also, if you think about slipping the IS services on that box, it is my understanding that's a SQL Server license consumed and given the ugliness that is the new per core licensing model on 2012, I wouldn't be happy writing that cheque. Not saying you'd do that, just a headache I saw at a client site when the auditors stopped by.
As a preface, I have done some checking around on this issue but found nothing that solves my question. This question was the closest I found but the answer did not resolve my issue.
Information about configuration: My local machine is Windows 7 with Visual Studio 2012 Update 3 and SSDT-BI installed. On the server machine I have SQL Server 2012 Developer Edition installed on Windows Server 2012 Standard. The data is coming from a third party database installed on a CentOS5 server.
I am trying to deploy a cube to my Analysis Services server, but I am getting the following error: "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running."
I have checked and the SQL Browser service is running both on my local machine and the server machine. As well, rather than connecting via < Server Name >\< Instance Name > I have tried connecting with IPAddress:Port.
I'm not sure if this is relevant, but in case it is: the database I am using to define the cube I'm trying to deploy is on a different server and has different authentication than my SQL Server 2012 Instance. Moving the data to the SQL Server is not an option.
To FrankPl: just to chime in, you answered my question a few hours ago which is essentially the same problem: VS2012 Pro with SSDT-BI installed, also Update-3 and the Aug.2013 update to AS. We're unable to connect and/or open a project.
I ve done some research and i can't seem to find anything similar to this.
I have an SQL Database from Windows Azure with several tables. I can log in just fine and view all the table data of all tables, except from a specific table.
When I click on the "Data" section of that specific table, my screen just goes completely blank and then I can't do nothing about it, apart from starting over. Any thoughts on this ?
(I have the latest version of Silverlight installed and I ve tried with Chrome,Firefox and Opera)
Thanks
You can use SQL Server Management Studio (SSMS) 2008 R2 for browse or what ever the task you have to do with SQL azure database as a alternative for your way of method.
Using SQL Server Management Studio 2008 R2 to Manage SQL Azure sample screen is as below.
For more information check this out Getting Started with SQL Azure Development
UPDATE
If you're going to use express edition, then you have to use SQL 2012 express with Win 8.
Check this out SQL Express Edition 2012
I hope this will help to you.
I have just upgraded to the Azure 1.7 sdk and have now lost the contents of my devstorage.
I can still see it in the local instance of sqlexpress (as DevelopmentStorage20110606), but when I use UseDevelopmentStorage=true, it longer connects to this.
Where has the new development storage db gone? I need to import my data from the previous version, as we use local storage for testing on the build server and have test data setup on it, or is there an upgrade script to be able to port this data accross.
Thanks
SDK 1.7 now uses IIS Express (compute) and SQL Server 2012 Express LocalDB (storage). You should be able to point your emulator to your existing database by running dsinit.
Michael Collier talks about the 1.6 vs. 1.7 differences in his post, here.
More information about LocalDB is here.
DSInit documentation is here.
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.