Worst Practices - Making On-The-Fly Changes
Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.
2003-01-20
7,777 reads
Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.
2003-01-20
7,777 reads
David Gugick, SQL Server performance expert and software developer, provides over 100 tips on how to boost SQL Server performance.
2003-01-17
88 reads
You have spent thousands of dollars on that cool technology; clustering, redundant controllers, redundant disks, redundant power supplies, redundant NIC cards, multiple network drops, fancy tape backup devices and the latest and greatest tape technology. You are all set. There is no way your going to have downtime. Right?
2003-01-16
4,925 reads
Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
2003-01-14
7,063 reads
For most DBAs, normalization is an understood concept, a bread and butter bit of knowledge. However, it is not at all unusual to review a database design by a development group for an OLTP (OnLine Transaction Processing) environment and find that the schema chosen is anything but properly normalized. This article by Brian Kelley will give you the core knowledge to data model.
2003-01-13
18,731 reads
Continuing on looking at demo servers, this article presents an interesting solution to ensuring consistent demos that was deployed out in the field for a client company.
2003-01-13
3,636 reads
Microsoft tells us why it's so important to defend your code against malicious attacks.
2003-01-10
243 reads
The challenge for Robert Marda was to devise a way to keep the data available at all times while importing the new data, detect if a full or daily update was received and run appropriate data pumps, put in sufficient fail safes to ensure bad data would not get imported, and to make the process automatic including notification to pagers upon failure. Robert shows you how he did it here.
2003-01-09
8,219 reads
Are you using default values for your parameters? Using named parameters when you call the proc or passing the values by ordinal? Should you be? Andy thinks 6 out of 10 of our readers will agree with his point of view, we'll be a little more conservative and guess that 5 of out 10 will be closer.
2003-01-08
8,237 reads
Steve discusses a potential new project we have in the works. We'd appreciate as many comments and votes on this one as possible.
2003-01-06
7,951 reads
By Steve Jones
I’m not sure I knew identity column values could not be updated. I ran...
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
I have mentioned this several times over several years. Can someone please help me...
SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers