sp_RestoreScript 1.9 – a dirty little bug squished!
It look like we had a little bug in sp_RestoreScript that was putting a rogue 0 after the backup file name. That’s now been fixed in 1.9. For information...
2021-09-16
74 reads
It look like we had a little bug in sp_RestoreScript that was putting a rogue 0 after the backup file name. That’s now been fixed in 1.9. For information...
2021-09-16
74 reads
This is something that comes up time and time again. A developer or member of the service desk comes up to me and says “SQL’s timing out, you see...
2021-07-27
79 reads
As always the code can be found here in our github repoWe updated our sample report here We forgot to mention V2.5! We added the ability to add Thresholds...
2021-07-23
107 reads
We all had those calls, it’s the middle of the night and we get that phone call that a customer is getting error messages due to their tempDB being...
2021-06-30 (first published: 2021-06-18)
737 reads
For one reason or another data security and encryption has been coming up quite a bit in my day to day work recently and I’ve started to realise that...
2021-05-21 (first published: 2021-05-17)
440 reads
A couple of years ago I wrote a post on how to generate a random number in SQL Server. https://sqlundercover.com/2017/06/22/generating-random-numbers-for-each-row-over-a-specified-range-and-other-funky-stuff-you-can-do-with-them/ It’s ok and it works, it’s also a method...
2021-03-31
3,957 reads
Blog posts have been few and far between from SQL Undercover lately but what better to try and get us back in the swing again than with T-SQL Tuesday....
2021-02-09
135 reads
All the changes for this release can be found in the Github Project page Mainly bug fixes this time around , but we have also added new functionality: Improvements...
2020-12-01
37 reads
This is one of them little options that I see which quite often gets little consideration or gets set to a user database without consideration of what the consequences...
2020-12-09 (first published: 2020-11-30)
392 reads
It looks like there was a bug lurking in sp_RestoreScript that was causing the wrong ALTER DATABASE command to be generated when using @SingleUser and a WITH MOVE parameter....
2020-11-23
46 reads
By Steve Jones
This value is something that I still hear today: our best work is done...
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Comments posted to this topic are about the item Planning for tomorrow, today -...
We have a BI-application that connects to input tables on a SQL Server 2022...
At work we've been getting better at writing what's known as GitHub Actions (workflows,...
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping AS SELECT cl.CityNameID, cl.CityName, o.OrderID, o.Customer, o.OrderDate, o.CustomerID, o.cityId FROM dbo.CityList AS cl INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID GO CREATE OR ALTER FUNCTION GetShipCityForOrder ( @OrderID INT ) RETURNS VARCHAR(50) WITH SCHEMABINDING AS BEGIN DECLARE @city VARCHAR(50); SELECT @city = os.CityName FROM dbo.OrderShipping AS os WHERE os.OrderID = @OrderID; RETURN @city; END; goWhat is the result? See possible answers