One way of getting the advantages of the Cloud without having to migrate the entire database is to just maintain a copy of the data that needs to be accessible to internet-based users in Windows Azure SQL Database. There are various ways of keeping the two in sync, and Feodor Georgiev describes a solution based in using SSIS.
2013-05-28
3,252 reads
It is increasingly likely that DBAs are now given responsibility for maintaining Azure SQL databases as well as conventional SQL Server databases. What is likely to be required by way of maintenence? What are the differences? Grant Fritchey covers what you need to know.
2013-05-20
2,964 reads
SQL Server Integration Services (SSIS) can be used effectively as a tool for moving data to and from Windows Azure SQL Database, as part of the total extract, transform, and load (ETL) solution and as part of the data movement solution. SSIS can be used effectively to move data between sources and destinations in the cloud, and in a hybrid scenario between the cloud and on-premise. This paper outlines best practices for using SSIS for cloud sources and destinations and for project planning for SSIS projects to be used with Azure or hybrid data moves, and gives an example of maximizing performance on a hybrid move by scaling out the data movement.
2013-02-19
2,061 reads
Amazon RDS SQL Server is the new kid on the block. Is it better than SQL Azure?
2012-07-11
10,426 reads
Before creating a data application in Windows Azure, it is important to make choices based on the type of data you have, as well as the security and the business requirements. There are a wide range of options, because Windows Azure has intrinsic data storage, completely separate from SQL Azure, that is highly available and replicated. Your data requirements are likely to dictate the type of data storage options you choose.
2012-05-22
2,650 reads
Developers targeting the SQL Azure platform should make sure their applications are secure. This article walks through the considerations developers need to keep in mind when designing SQL Azure applications.
2012-03-12
2,138 reads
As a DBA you always followed a practice to back up your database (or take a snapshot of your database) before making any changes so that you can revert to your old database state if something goes wrong. Also to setup a development or test environment you use a backup of your database and restore it in the respective environment. If you are moving to SQL Azure, what would you do in these cases as backup / restore and database snapshots are not supported as of now?
2011-02-10
3,731 reads
Learn how you can connect to a SQL Azure database.
2011-01-27
1,945 reads
SQL Azure provides features similar to a relational database for your cloud apps. We’ll show you how to start developing for SQL Azure today.
2011-01-14
3,003 reads
Most business applications you write probably utilize some kind of relational database. And, as a .NET developer, the chances are that database is Microsoft SQL Server. This article walks you through migrating your SQL Server database applications to the cloud with SQL Azure.
2010-09-27
3,374 reads
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
By Steve Jones
I saw some good reviews of the small gemma3 model in a few places...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item We Should Demand Better
Comments posted to this topic are about the item Estimated Rows
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch? See possible answers