If you are a SQL Server DBA, you realize that the performance of cursors is not great and they should be avoided where possible. One place it is difficult to avoid cursors is individual row processing within a trigger. Amin Sobati brings us a new article that shows just how you can avoid this.
2007-12-28 (first published: 2006-12-07)
47,970 reads
Writing complex queries can be a little tricky, especially when you get into outer joins and inequalities. New author Amin Sobati takes a look at a tricky situation with the "Not Equal To" operator and shows how you can avoid inaccurate results.
2006-08-23
14,844 reads
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Quite the title, so let me set the stage first. You have an Azure...
By HeyMo0sh
In the realm of software development and content creation, the deployment pipeline serves as...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers