My “Success” story describes the import process when it works without a hitch, while my “Challenge” story highlights a common difficulty encountered when using the Microsoft Import and Export Wizard, and then offers a solution.
Most people prefer to work with the platforms that they are familiar with, but there is always pressure to try new, exciting technologies when others have success. Steve Jones explores the idea of switching platforms.
Besides the technical skills required to be a proficient SQL Server business intelligence developer, there are numerous "soft" skills that can contribute to your success.
It is widely acknowledged within the SQL Server community that baselines represent valuable information that DBAs should capture. Unfortunately, very few companies manage to log and report on this information, and DBAs are then forced to troubleshoot from the hip and scramble to find evidence to prove that the database is not the problem. This article will make a compelling argument for why DBAs must start capturing baseline information, and will create a roadmap for subsequent posts.
What's the most important thing about your application? The code? The accuracy of its calculations? The layout of the reports? Steve Jones has another opinion.
Aaron Bertrand supplies a script which generates two separate sets of commands: one to drop all foreign key constraints, and one to create them again. These scripts are stored in a table so that, if you drop the constraints and then disaster of some kind strikes during the create, you still have everything handy and can troubleshoot if needed.
This article shows a problem with P2P replication doesn't replicate DDL schema changes and something you might want to check.
Who checks on those who manage our systems? Is there auditing in place for those accidental DBAs?
When you're importing data into an RDBMS in bulk and an exception condition is raised because of a constraint violation, you generally need to fix the problem with the data and try again. The error won't tell you which rows are causing the violation. What if you've thousands of rows to search when it happens? There are solutions, writes William Sisson.
Where do you start fixing a SQL Server crash when there isn’t a single clue? The DBA Team had better find out quick, or they’re not going to get any sleep tonight. Find out how it all goes.
By Steve Jones
Thanks for attending my sessions. Resources below: Slides: Using Data API Builder GitHub repo: ...
By Steve Jones
Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...
By Steve Jones
I was creating a question on sp_readerrorlog and realized that this procedure is different...
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
Comments posted to this topic are about the item The Disabled Index
Comments posted to this topic are about the item Server-Level Table sizes
I run this code on SQL Server 2022.
CREATE TABLE Drink
(
drinkid INT NOT NULL
CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
drinkname VARCHAR(20),
rating NUMERIC(2, 1)
)
GO
INSERT INTO Drink
(
drinkid,
drinkname,
rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result? See possible answers