Cross Database Queries are possible - azure

Can I do cross database queries from a Azure SQL Database to Azure SQL Data warehouse, I read somewhere that its possible around sql databases but can it be possible in azure datawarehouse and sql database.

It is a "thing" with MS SQL databases, achieved via links using special credentials and external tables (which essentially map a foreign DB's tables to the local DB). It didn't used to be possible in Azure, but it is nowadays.
For more info, see here

Related

Is there any way to querying two tables from two different database without using external table in Azure SQL?

I have to querying two tables from two different databases in Azure SQL. Is there any option available in azure?
If your database are Azure single databases, maybe you can use OPENROWSET (Transact-SQL). It now support Azure SQL database.
Includes all connection information that is required to access remote data from an OLE DB data source. This method is an alternative to accessing tables in a linked server and is a one-time, ad hoc method of connecting and accessing remote data by using OLE DB. For more frequent references to OLE DB data sources, use linked servers instead. For more information, see Linked Servers (Database Engine). The OPENROWSET function can be referenced in the FROM clause of a query as if it were a table name. The OPENROWSET function can also be referenced as the target table of an INSERT, UPDATE, or DELETE statement, subject to the capabilities of the OLE DB provider. Although the query might return multiple result sets, OPENROWSET returns only the first one.
Hope this helps.

SQL Server to Azure Cosmos DB Migration

Please let me know whether we can migrate stored procedure from Microsoft SQL server to Microsoft Azure Cosmos DB ?
Either with DocumentDB migration tool or any other tool
There's really no direct correlation between the two: Stored procedures within the two databases are completely different. No possible way to migrate them, aside from you doing a complete rewrite. SQL Server stored procedures are written in SQL, vs Cosmos DB's JS-based stored procedures. Plus there is the notion of partitions, context, etc.
And Cosmos DB doesn't offer SQL Server compatibility and isn't a relational database. The Core (SQL) API takes advantage of SQL query language, but only for queries.

tutorials on migrating SQL 2008 BI-stack to Azure SQL Data Warehouse?

Are there any tutorials available on the subject of migrating from an existing BI-stack based on SQL Server 2008 to Azure SQL Data Warehouse? I'm specifically interested in best practices with regards to how to handle cross database joins on non-premium tiers (our existing procedures and UDFs are full of joins on multiple database objects) and how to migrate existing SSAS cubes and its related programmability and ETL.
What BI-stack are you using? This will determine your next steps for the actual BI tools.
Specifically for cross-database queries when moving to the cloud, the guidance is to move the databases into schemas and then update your scripts to use schema based (2 part names) vs. database (3 part names) when referencing objects. For example, if you have staging and production databases you can simply move your staging objects into a [staging] schema within a single database.
Azure SQL Data Warehouse is commonly used as a backing store for SSAS cubes (MOLAP/ROLAP/Tabular mode). In the Azure cloud, customers have created IaaS SQL Server VMs to host ETL process (SSIS) and cubes (SSAS) with direct connections to SQL Data Warehouse.

Can't query between databases in SQL Azure

I have a SQL Azure Database Server and I need to query between the Databases but can't figure out how to accomplish this.
Here is the structure of my databases:
Server.X
Database.A
Database.B
Database.C
In Database.A I have a Stored Procedure that needs to retrieve data from Database.B. Normally, I would reference the database like SELECT * FROM [Database.B].[dbo].[MyTable] but this does not appear to be allowed in SQL Azure.
Msg 40515, Level 15, State 1, Line 16
Reference to database and/or server name in 'Database.B.dbo.MyTable' is not supported in this version of SQL Server.
Is there a way to do this on the database end?
In the final version Databases A & C will both need data from Database B.
Update:
As per Illuminati's comment and answer, the situation has changed since this answer was originally accepted and there is now support for cross database queries as per https://azure.microsoft.com/en-us/blog/querying-remote-databases-in-azure-sql-db/
Original Answer (2013):
Cross database queries aren't supported in SQL Azure. Which means you need to either combine the databases to prevent the need in the first place, or query both databases independently and basically join the data in your application.
Cross database queries are now supported in SQL Azure
https://azure.microsoft.com/en-us/blog/querying-remote-databases-in-azure-sql-db/
Azure SQL DB is previewing Elastic Database Query feature at this point in time that will help you query among Azure SQL DBs with some limitations. You can get detailed information about the feature here.

Azure Table Storage Database Diagramming

I'm wondering what the professional way is to create a database schema for a Azure Storage Tables database (not SQL Azure).
For a datawarehouse you usually make a starscheme or snowflake (OLAP cube) and for a database with a lot of transactions you'd probably make a normalized relational database (SQL Azure/SQL Server). But with Azure Storage Tables there aren't any relations to make so what's the best practice for creating a professional Azure Storage Tables database?
So, Azure Storage tables do not have schema. When you save an object to an azure table, that object is just there. You do not create schema for a table. Visualization tools, like Cerebrata's Storage Studio or Visual Studio's table viewer attempt to visualize the data in the azure table as columns, but in reality, all they're doing is showing you properties of objects as columns for convenience.

Resources