Windows Azure Sql Database Management Portal Error - azure

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.

Related

Deploy Azure SQL Elastic Database query

I have multiple Azure SQL databases. One database holds all the staging table and the other database holds all the fact/dim tables. Now in my development environment I have stored procedure which reads data from staging tables (from staging database) and loads the data into its respective fact/dim tables (in a different database).
The above scenario is all working fine. I have multiple SQL projects for each database.
Now how do I deploy the elastic database queries while deploying the dacpac?
Below is the error when I add the elastic queries as a part of my post deployment scripts in Visual studio and try to build it.
PS: The SQL project properties is set to target the V12 version of the Azure SQL Database
Which version of the SQL Server Data Tools (SSDT) are you using? If you are not using the latest (14.0.60413.0), give it a try to upgrade SSDT: https://msdn.microsoft.com/en-US/mt429383. With that version, I am now successfully able to compile and publish database projects and dacpacs.
To successfully build, you will need to install the latest SSDT Preview which includes support for these objects from here. Support for the latest Azure SQL DB and SQL Server 2016 features is only available in the Preview for VS2013 at present, whereas for VS2015 the support was shipped in VS2015 Update 2. Once SQL Server 2016 goes GA (June 1, 2016) an RTM update will be pushed through the Visual Studio 2013 Extensions and Updates channel containing this support. That will ensure you get monthly updates with the latest changes again.
Note that even with the latest bits, if you open the file itself you'll get an issue with the Intellisense parser. Building the project will work fine but on opening a document you will see the errors appear for that specific document. Note that the same issue occurs in SSMS when coding this into a query window. This is because the Intellisense parser is separate from the core build system. The fix for this is in progress and will land in a post-SQL Server 2016 update (likely late June - July timeframe).
Disclosure: I work on the SQL Server tools team.

Incompatible MS SQL server version with devexpress version 15.x

I'm trying to add a Project Data Source in a GridView in DevExpress.
I click on the little arrow on the above right of the Gridview. I choose 'Add project Data Source'.
Then I choose, a Data Type source => DATABASE.
Then, 'Database model' =>DATASET.
Then, for 'Data connection' I choose MS SQL Server.
I then choose the server and I get a pop-up windows that says:
This server version is not supported. You must have SQL Server 2005 or later.
Now, I've confirmed that the server I'm trying to connect to has Microsoft SQL Server 2000 installed on it.
I know that some people got that pop-up window when trying to use Microsoft SQL Server 2008. It was apparently a Visual Studio issue.
I just want to confirm that this message that I'm getting is legit. (It would seem right, seeing, as I
mentionned earlier, I have Microsoft SQL Server 2000 installed. ) For some reason, I still
think it's weird that I'm getting this message. I have Microsoft Visual Studio 2012 by the way. Can anybody confirm this.
I do not think that this issue is related to DevExpress control. It is common issue with visual studio when you SQL Server that Visual studio IDE does not support or missing SQL Server Data Objects.
I suggest you to check below link for your confirmation that SQL Server is not supported in newer IDE directly.
This server version is not supported. You must have Microsoft SQL Server 2005 Beta 2 or later.
SQL Server 2000 and Visual Studio 2010
This Server Version is not supported. You must have SQL 2005 or later (VS2010 Problem)
Some how you can use quick fix to connect with the data base and write code to do other operations.
Connecting SQL server 2000 using Visual Studio 2012
.NET Framework Data Provder for OLE DB -> Microsoft OLE DB Provider
Hope this help you understand the real issue behind this.

Why is SQL Server Compact not available from Add New Item -> Data?

Why is SQL Server Compact not available from within a Web API project when right-clicking the project's "App_Date" folder and selecting Add -> New Item... -> Visual C#" -> "Data?
According to this tutorial on adding a database to an ASP.NET Web API project, there should be, not only these options there:
SQL Server Database
XML File
XML Schema
...but also "SQL Server Compact 4.0 Local Database"
Yet I only have those first three available. Why?
The tutorial linked to above was written on on May 30, 2013, and it specifies Visual Studio 2012 whereas I'm using Visual Studio 2013. Did "SQL Server Compact 4.0 Local Database" get dropped in VS 2013?
If not, how can I restore SQL Server Compact to the selection of available options?
Yes, SQL Compact Local Database was removed in VS 2013, but you can use the Sql Ce Toolbox to manage your database, and manually include a SQL Ce file in your web app.

Where does Orchard CMS create its built-in SQL Server Compact Database

You can configure Orchard CMS to use a built-in SQL Server Compact database.
I want to connect to, and query, this database.
Where does Orchard create it?
The database is created in:
src/Orchard.Web/App_Data/sites/YourSiteName
To connect to it I use the following plugin for Visual Studio:
SQL Server /SQLite Toolbox
For other ways to open SQL Compact databases see this SO question:
How do you open an SDF file (SQL Server Compact Edition)?
Using the development installation of Orchard, the CMS creates the SQL Server CE .sdf file in the src/Orchard.Web/App_Data/sites/NameOfTheSite directory.
You can connect to it using SQL Management Studio (up to 2012) by following these steps:
1. File -> Connect Object Explorer...
2. Change 'Server Type' to 'SQL Server Compact Edition'
3. Select < Browse for more...>
4. Browse to and select your .sdf file.
For versions of SQL Management Studio 2012 and above, a third-party tool is required.
See this question for further details.

(localDB)\Projects or (localDB)\v11.0

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

Resources