Although most of what you read tells you to stay away from dynamic SQL, the reality is there are places where writing T-SQL code dynamically just makes sense. The one downside to dynamic SQL is that if it is not written correctly the code will fail. Eli Leiba shares a function that he created to help determine if the dynamic code is OK prior to execution.
2017-08-14
5,638 reads
The majority of Azure SQL Database related features reach their General Availability (GA) stage relatively quickly. There are however, some exceptions. The most prominent example in this category is likely Azure SQL Data Sync, which has remained in Preview since its introduction 7 years ago. Fortunately, there are signs that this service might be finally reaching production-ready state. In thius article, Martin Policht will introduce its main characteristics.
2017-08-11
4,501 reads
It is possible to do a great deal with R within SQL Server, but it is best to start by doing analysis in R on numeric data from SQL Server and returning the results to SQL Server. There is great value to be gained even with this basic foundation. Robert Sheldon is on hand to give you a kick start with the first in his series on beginning with R in SQL Server.
2017-08-10
7,279 reads
This paper shares the approach used to understand and determine: 1) Using ‘Hekaton’ in SQL Server 2014 against RPM, including performance analysis. 2)
Understand the specifics involved while migrating to Hekaton.
2017-08-09
3,784 reads
Erik Darling wonders why SQL Server doesn't have more granular parallelism options.
2017-08-09
3,671 reads
In order to be able to deliver database changes more quickly, there are several tasks that must be automated. It can be a daunting job to ensure that the whole team has the latest database build when there is a proliferation of copies, and the database is big. Phil illustrates a solution by taking a set of Redgate tools to show how they can be used together, via PowerShell, to build a database from object-level source, stock it with data, document it, and then provision any number of test and development servers with the database build, taking care to save any DDL changes to the existing copies of the database.
2017-08-08
5,020 reads
Serget Gigoyan is back with another set of 5 common SSMS tips.
2017-08-07
4,928 reads
You may have already experienced ETL Hell, where you have a large number of similar of SSIS tasks, and a small change, such as an alteration to the network topology, means that they all need to be altered with the correct connection details. Perhaps you should consider creating design patterns for all the standard components of integration tasks in BIML, and generating the SSIS packages from these? Amarendra walks you through the process.
2017-08-04
6,028 reads
Siddharth Mehta shows that R libraries can be used from T-SQL to ingest data from the web into SQL Server.
2017-08-03
5,113 reads
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
2017-08-02
8,420 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers