Please forward this to the systems admin in your life that wants to take your big SQL Server, and cram it into a Virtual Machine against your wishes.
So you’ve got your kick ass virtualization project moving along nicely, but you’ve hit a snag. The DBAs are fighting back saying that they don’t want to virtualize the SQL Servers. You hear them, but you know better right? You built the hardware, you know what it can do. The SQL Server doesn’t really need all that horse power. Continued »
If you work with any of the other big database platforms you’ve probably noticed that SQL Server’s implementation of a unique index is “different” than the others. Until now there hasn’t been a way to fix that without using a trigger. Until now… Continued »
If you follow me on twitter then you’ve heard bits and pieces of this already on my twitter stream.
In preparation for the onslaught of security patches which were released on October 14, 2009 I went ahead and patched all our severs the day before as it had been a couple of weeks since I had triggered patching and I wanted to get everything else installed so that there wouldn’t be any dependency issues with installing the new patches. All of our servers, about 60 in all, patched correctly except for two of the three servers which host our web application which our customers use. Now I say that two of the three servers didn’t patch correctly, but the third server wasn’t allowed to reboot so I don’t know if that one patched corrected or not at the time. But with two machines of the three offline, I wasn’t willing to chance it. Continued »
I posted a survey over on Security Fight Club to get some input from the SQL community. I need to know what color I should die my hair for SQL PASS. The survey will be open until shortly before PASS at which point I’ll announce the winning color.
PS: I would have posted it here directly but this isn’t my site, so I can’t add plugins to handle this sort of stuff here.
That’s right folks. Once you upgrade SQL Server versions there is no going back. Continued »
Another major data loss is showing that if you want to keep your data, its up to you to back it up. T-Mobile customers who have a sidekick phone are being told this weekend that they shouldn’t turn off their cell phones. If they do they will loose their address book data and anything else saved on the phone. Apparently there are some major data center problems going on over at Danger (the folks who make the Sidekick) and the Sidekick relies very heavly on the servers in the Danger data center. Apparenly there have been problems going on for a couple of days now. So far there’s no planned update from T-Mobile until Monday.
The problems are serious enough that T-Mobile has suspended the sale of the phone, and posted a very serious notice on there forums “Sidekick customers, during this service disruption, please DO NOT remove your battery, reset your Sidekick, or allow it to lose power.”.
This is just another indicator that you need to be responsible for backing up your data. You also need to know how your devices work. Personally I have a blackberry and it is synced up with my Exchange server. I know that if something happens to my Exchange server, I know that my local copy is fine. Same goes if there is a problem with RIMs servers.
Don’t rely on your service provider to backup your device, if you want to keep your data back up the data your self. If your phone provider doesn’t offer a way to back it up, check on the internet. Most cell phone models have some way to back them up so that you don’t loose everything if something goes wrong.
Over on the SecurityFightClub.com site I wrote a post about why database servers shouldn’t be on the Internet.
I recently published an article on SearchSQLServer.com about DTS and SSIS where I talk about some of the differences. Obvsiolly I didn’t cover all the differences between DTS and SSIS, just some of them. So don’t go railing on me that I didn’t cover something.
Shhh… Don’t tell anyone, put I’m planning on sneaking into Quest’s presentation this Friday (which in itself is a feet when half the people there know you by site) grabbing some of the free lunch, and giving a quick presentation on Virtualization. Continued »
When installing SQL Server 2005 SP3 you may get an error about the password being to short, and it may have nothing to do with your sa password. It’s because the Install Scripts are trying to create a certificate with a password which doesn’t meet your domain’s password requirements.
If you get this error navigate to the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade folder. Find the script for upgrading the SQL Agent. Open the script and find the CREATE CERTIFICATE statement. Make the password longer. In my case I added 123456@ to the end of the password. The password is in two different places in the script.
Then open Add/Remove Programs and select SQL Server 2005 and select Change. Then run though the wizard to complete the installation of the service pack.