Out of all the problems you can have with SQL Server troubleshooting connectivity issues can be the most challenging. When you factor in the complexities of Active Directory and SQL Server’s interaction with it fixing SSPI errors can be down right baffling...
2009-07-23
4,833 reads
Microsoft has always been pretty good at one thing, ease on install. One of the things I always says is the greatest thing about SQL Server is any idiot can install it. The other thing I also say is the worst thing about SQL Server is any idiot can install...
2009-07-01
4,332 reads
I read, a lot. I’ve been a prolific reader all my adult life. I use to split my reading between tech books and my regular relaxing reading but since I got into audio books several years ago I just pretty much read tech books now. Some times I’ll listen..
2009-06-22
2,905 reads
Having been married to Microsoft for most of my professional career doesn’t mean I drink the Kool-Aid. I have had the distinct privilege to grow up in interesting times. I loved DOS. As a BBS operator DOS was the de facto OS for most BBSes that ran on..
2009-06-19
3,001 reads
We got something good in the mail last week! Some quick observations: The build quality is outstanding. Nothing cheap at all about this card. The engineering that has gone into this shows in every way. It is made up of modules that...
2009-06-15
1,479 reads
I do more than just SQL Server. I enjoy programming. In my former life I have worked with C/C++ and Assembler. I also spent quite a bit of time in Visual Basic. I loved it for prototyping and what we now call RAD development efforts.
2009-06-08
3,393 reads
It doesn’t happen often but every once in a while you may be the lucky person to find a previously unknown bug in SQL Server.
2009-06-05
4,014 reads
I’ve often described SQL Server to people new to databases as a data pump. Just like a water pump, you have limited capacity to move water in or out of a system usually measured in gallons per hour. If you want to upgrade your pumping systems it can be...
2009-04-21
6,824 reads
Often I tell clients better to much memory than too little. This can be applied to any database engine essentially. If your data set is growing over time you will end up using any memory that is not consumed today.
2009-04-15
3,029 reads
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). Wesley Brown has taken four of these products into his environment and run some comparisons. Read about large databases in part 2 of this series.
2004-12-09
7,294 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers