New answers tagged export
You can create views using LIMIT and give those view names to the end users. If you're using a development tool such as DBVisualizer, you can set the number of records to limit. As always, query labels allow for easy tracking of any requests.
I have not actually tried this (but it peaks my interest to later). You will not be able to use Restore-Database because it only reads native backup formats from SQL Server, not Azure SQL. The BACPAC file created from your backup of an Azure SQL database is in a data-tier format. Which in this format contains the schema and data for the database. In order ...
From your issue, I can see that your choice of tool is a problem. Below are 2 options that you can use : Backup on the source server with COMPRESSION and Restore it on the destination server. Make sure you have Instant file initialization enabled. Once Restore is done, you can delete unwanted objects (if you want). Use BCP OUT in native mode on source ...
SQLCMD can be used to export data. The default output is sometimes unwieldy for that, but you can use some command-line options to turn off the headers, trim trailing spaces, and to use a comma separator instead of the default space: sqlcmd -Q "SET NOCOUNT ON; SELECT TOP(10) name, object_id, type FROM sys.objects;" ^ -h-1 -W -s "," Returns: ...
Top 50 recent answers are included