Azure

External Article

Windows Azure SQL Database (WASD) Primer

  • Article

Are you a SQL Server DBA who is now being asked to migrate databases to Windows Azure SQL Database (WASD)? Are you a developer who is writing code for a cloud service that shall use SQL Database as the back-end? This blog post is based on issues encountered while supporting customers that were once in your shoes and the lessons learned in the process.

2013-11-18

3,173 reads

External Article

Uploading Data to Windows Azure SQL Database

  • Article

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

External Article

Azure SQL Database Maintenance

  • Article

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

Technical Article

SSIS for Azure and Hybrid Data Movement

  • Article

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

External Article

Windows Azure from a Data Perspective

  • Article

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

External Article

SQL Azure - Creating backups and copies of your databases

  • Article

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

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCU KUNINGAN,Telp/Wa 0821.3111.159

By gopalchettri

Cyber 2, Gedung Menara Karya, Jl. H. R. Rasuna Said Ground Floor, RT.7/RW.2, Kuningan,...

BCA KCP Kas Petisah Tlpn/wa:085373737551

By philipjadler

Jl. Kota Baru 3 No.6, Petisah Tengah, Kec. Medan Petisah, Kota Medan, Sumatera Utara...

BCA KCP Setiabudi Tlpn/wa:085373737551

By philipjadler

Jl. Setia Budi No.150 A-B, Tj. Rejo, Kec. Medan Sunggal, Kota Medan, Sumatera Utara...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers