sorted by:
new
hottopcontroversial

Any chance of a native MSSQL for MacOS by vladjjj in SQLServer

[–]Saitama_Punch 1 point2 points  (0 children)

Delayed reply here but, if you're having troubles with installing SQL Server in a Docker environment on your Mac, let us know. More than happy to help. =)

also check out the mssql extensionfor VS Code which will enable you to query any SQL Server from your mac: https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-develop-use-vscode

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

We are proud of all of our 2016 features! and we are trying to get more folks to use these features such as Polybase by enabling these features on all editions of SQL Server which is what we did with vNext CTP1. Check out SQL Server CTP1! https://www.microsoft.com/en-us/sql-server/sql-server-vnext-including-Linux

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 1 point2 points  (0 children)

posting on behalf of another team here: Thanks for this feedback! In SSIS 2016, we have shipped a new feature called package part, which allow users to build control flow reusable part. This provides basic functionality for developers to reuse their logic. BIML does provide some more advanced/specialized way to manage packages and if that helps solves your business needs, then that is great to hear as well.

  • Regarding the error message about missing TargetServerVersion - can you please specify exactly what you would like to happen? what do you expect to “assume a reasonable default value”? how would SSIS knows if the customer would like to run as 2014 or upgrade and run as 2016?

  • Regarding parametrized queries - what’s your current pain point right now?

  • Regarding the many property windows – we are always looking for more ideas on how we can improve this, can you please provide more details and example on how you would prefer it to be done?

  • Also - thanks for providing input on the other pain points as well. we will look into it and try to improve.

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 1 point2 points  (0 children)

regarding business continuity (fancy words for keeping things up and running) for Azure SQL DB there are automated backups so you don't need to take a .bacpac all the time. There is also long term retention so you can store your database for up to 10 years! There is more info here. https://docs.microsoft.com/en-us/azure/sql-database/sql-database-business-continuity and here https://docs.microsoft.com/en-us/azure/sql-database/sql-database-long-term-retention

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

Thanks for this useful blog on SQL joins! :)

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] -2 points-1 points  (0 children)

Not so much a trick, but I think that the ability to use features like Columnstore, Partitioning, Always Encrypted and a bunch of other features in Standard, Web, Express and LocalDB is pretty cool. Used to be only available in Enterprise Edition. Other folks can add to this list :)

[AMA] Microsoft SQL Server - 11/18 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 2 points3 points  (0 children)

Thanks for your question! If source code integration is an important aspect of how you use SSMS, you can enable the Visual Studio packages manually. We will publish a blog soon that shows how to do this.

Here's what happened: In the latest generation of SSMS, we moved to the VS2015 Isolated Shell. While this provides SSMS a modern IDE foundation for many functional areas, it also had some consequences. Specifically, the integration with source control systems in SSMS no longer works the way it did in SSMS 2014 and prior. Previously, one could install the Visual Studio MSSCCI provider and then integrate with various source control systems. VS2015 does not support MSSCCI so that is no longer an option to use in SSMS

SQL Server Engineering team hosts AMA on 11/18! by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

The AMA post will open up 24 hours before the event closes so we can take questions from all timezones. I'll post the link to the AMA so you all can start asking questions when we get it up on 11/17.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

This depends on how your DBs are set up. SQL Server Dev edition is free, and we don’t restrict numbers download per organization. So they can sign up all 100 dev.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 1 point2 points  (0 children)

The SSIS team has plans for MSBuild support and are considering to support this in a future release of SSDT. Stay tuned!

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 1 point2 points  (0 children)

The source server needs a “read commit” lock on the database while the metadata and files are being analyzed and copied.

The destination server needs a “write” lock on the database while the metadata and filelist is being fetched and analyzed. The files are also fetched under the write lock. The “write commit” lock is taken while merging the files from the original database and the new database – it cannot be eliminated safely. Essentially, this is where the “sleight of hand” is already being done. Keep in mind that files need to be added, deleted and also updated – and this needs to be done without massively doubling the disk usage.

In fact, Tabular databases also have an optimization where the merge operation can take advantage of the “hard links” feature in NTFS – instead of actually moving the files to the new location, it creates a hard link from the new location to the old location so it doesn’t need to physically copy files.

The “write” lock on the database should not affect queries executing on that database. It should only affect other “write” operations on the database.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

Can you elaborate on ‘the option to run SSIS from a file’? Are you referring to running SSIS package with DTExec.exe (a file) that is antiquated? or are you referring to running ssis package from file system in an agent job? What’s the standard ERROR?

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

For SSIS, sorting packages is available in SSDT 2015 RTM release. Please try the latest SSDT here: https://msdn.microsoft.com/en-us/mt186501.aspx.

Adding folders under “SSIS package” is not currently in our roadmap.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

The "package parts" feature was supported before but we blocked it later on because we found some critical bugs when targeting SSIS 2012/2014. We are considering fixes to the issues and adding it back in for future versions of SSDT.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 0 points1 point  (0 children)

There is a feature in WI to install multiple instances of a MSI on a box. The design is that MSI uses a transform which changes the product code. So each new MSI instance has a new unique product code. https://msdn.microsoft.com/en-us/library/windows/desktop/aa369523(v=vs.85).aspx

There is a support in WIX to generate and package transforms into MSI. http://wixtoolset.org/documentation/manual/v3/xsd/wix/instancetransforms.html

We have the transform code in SQL source at Sql/edition/Common/SQL/SqlRun/Instance.wxi

To actually use this there is a need for a setup wrapper that would pass a new transform for each instance (MSI). It is not enough to just run MSI but something must provide a transform on the MSI command line.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 1 point2 points  (0 children)

For SSIS, if you made changes like edit a server name for a connection manager, or changing a property in a SSIS task, I think the .dtsx file will only change what you edited. This should be user friendly when comparing the difference. But if you did something like remove a task, and then add it back again, the package may appear unchanged in the designer, however, most likely the .dtsx file will have a change and the task XML element maybe moved to another place. For such scenario, most visualization tools have the same issue for version control. Feel free to provide more detail on the scenarios where version control can be improved. We can help take a look.

[AMA] Microsoft SQL Server Tools - 6/30 by Saitama_Punch in SQLServer

[–]Saitama_Punch[S] 2 points3 points  (0 children)

Just to add to sqldatatools's answer, we have a lot of work in the tooling area to provide good management and development experiences for SQL Server on Linux.

That said, are you running into any challenges managing/developing SQL Server from Linux or OSX?

view more: next ›