Sometimes when you work with data, you have to move a lot of data around. And one of the best tools to do it is SSIS (Sql Server Integration Services). It’s a flexible solution to move almost anything to almost anywhere. It uses a small piece of Visual Studio to create the “packages” (really just XML files) and even allows some level of .Net code inside.
But if you need to run the full Visual Studio installation alongside SSIS, you may run into some troubles. SSIS is installed together with SSMS, and due to some misterious circumstances you may end up with a non-working VS if you install or update something out of the exact order.
The latest info I got on this is that you will need SQL 2012 SP1 CU5 to fix it, if it begins to misbehave. Read on the tweets from @MsSQLGirl to check more details. She pointed this great blog post about it too.
It’s been a little while that I was thinking how would be the best way to share knowledge over this blog. And this is the first post on a series more focused on how to make our jobs easier. I thought of calling this section “SQL Freebies”, but I’m not sure all future programs will be free, so I decided to tag it ”SQL Tools”.
And tonight’s product is…. Red-Gate SQL Scripts Manager. This one is actually free. It’s a collection of nice scripts from great people out there, with a simple interface to run them against the SQL Server you want. Yes, it includes all the sources if you wanna to customize something. Below you have the download link:
I will give these a try. Actually I think they should even include some more scripts (just because I like stand-alone “packages”), like the one from Michelle Ufford already mentioned on this blog. BTW, this would be a gread time to go and check it there is any new version.
Nowadays storage is cheap (relatively
) and the problems of shortage of space are less frequent. But sometimes they do happen. And some of these times, someone could think enabling NTFS Folder Compression
is a good idea. Maybe it is, but just for one folder and not the whole drive. Especially drive C:.
Well, I have no idea why this ever happened. But Windows will allow you to do so on a folder with a live database (even
though it shouldn’t
) - at least it will do this if you compress the whole drive. And when you try to restore any database or create a new one on that drive, you will be greeted by this error:
Msg 5118, Level 16, State 3, Line 1
The file "C:\MSSQL\Your_File.ldf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
To fix it simply disable NTFS compression on the folder used by SQL. Or disable it for the whole drive. Well, never use it in the first place! cya!
I don’t know. But it seems we won’t have as much SPs as once we did. I just read a great article at SSC (short for SqlServerCentral, a great source of research) with this same question. And I agree with them completely: the cumulative update servicing model is ill-suited for server administration.
By installing a lot of smaller updates we will cause more downtime simply to reboot the sql service (or the whole server), even if we disregard testing completely (do NOT patch without testing! this was just an example!).
Read the full article below. Share it, spread the word, because it seems this change will affect MS OS and other products guys/gals too. Maybe we can make a difference.
Sometimes the past will strike you hard. And all of a sudden you are back to 10 years ago, dealing with bugs on Windows Registry settings and issues.
This weekend I spent quite a few hours trying to fix an unwanted behaviour of Windows 8.1 on my desktop, all via murky and mysterious keys. In the end, it kept disconnecting my USB hard drives and I had to re-format the whole thing (believe me, after you tinker on Regedit and it still doesn’t works, the next step is a clean install).
And now a Windows Server 2008 R2 box is complaining about registry keys marked for deletion, and will not let me restart any service or even logon to it. Searching the web was fruitless, as all I could find are old posts and no conclusive answer. The only fix? Restart the machine. That’s a really nice thing to be done on production servers, don’t ya think? [/sarcasm].
Anyway, with some teamwork from the OS team we discovered that we had a pending boot on that box. For some unknow reason the Windows Installer service went crazy after some updates that were pushed to the server, and blocked any new process trying to run. The only option left was to boot the server. Below you have the error message and some links about it.
Error 1018: Illegal operation attempted on a Registry key which has been marked for deletion
List of Windows System Error Codes: http://www.hiteksoftware.com/knowledge/articles/049.htm
The WordPress.com stats helper monkeys (ed note: monkeys? lol!) prepared a 2013 annual report for this blog.
Here’s an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 41,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 15 sold-out performances for that many people to see it.
Click here to see the complete report.
Times of change are ahead of us. Lately the technology reached some kind of plateau, with performance and features staying relatively at the same level for several years. Go and check the hardware market: despite some big savings on power, the fastest CPU cores from a couple of years ago are still in the “fastest block”. The same goes for software: from 2006 until 2012 we did not have the kind of big changes that happened a few years before.
I know, there were changes and improvements, of course. They were just not big as the changes that happened before. The end result is that we have fewer compelling reasons to upgrade. If not much changed, why hurry? But we must not let this keep us preventing from using the latest and the greatest. So go ahead, do your research and deploy the latest versions, there are incremental benefits waiting for you. And I’m not even talking about the cloud, this is a separate topic.
TLDR: here are some considerations for using the latest OS and SQL versions. Push forward, and if you have any considerations to share please fell free to add your comments on this post.
- SQL 2005 is not supported on Windows 2012
- Windows 8 comes with .NET 4.0, and SQL 2012 requires .NET 3.5 – enable it first
- SQL2008R2 has some issues with clustering on Windows 2012
For more details, please read the full article: http://support.microsoft.com/kb/2681562
SQL 2012 Express with SP1 download: http://www.microsoft.com/en-us/download/details.aspx?id=35579 (I’m still trying to find the stand-alone SSMS installer for 2012).
And for some benefits of using both the latest and greatest: http://blogs.technet.com/b/dataplatforminsider/archive/2012/12/06/the-perfect-combination-sql-server-2012-windows-server-2012-and-system-center-2012.aspx
R2 wave: http://blogs.technet.com/b/microsoft_blog/archive/2013/08/14/ve-the-date-windows-server-2012-r2-windows-system-center-2012-r2-and-windows-intune-update-coming-oct-18.aspx
I’ve stumbled upon this error when fixing my GF’s computer. Nowadays almost all servers on work environment are virtualized, so you can change the hardware atributes freely. But at home the story is different: you only have a handfull of hardware, and that’s it! No chance to mess around with terabytes of free space.
To make things clear: the builtin System Image tool of Windows (Vista/7/8,server2008/R2) will not restore to a smaller disk. It will always require a destination disk of the same size or bigger. Well, when you need to restore a system image it means something is really wrong with your PC, right? And this is a pretty dumb requirement, as most of the time the first part of a computer to die is the Hard Disk.
What leads me to my final situation: a dead hard-disk and a useless system imagem. I installed everything a few months ago on a 500gb HDD. Yesterday it started giving me bad sectors, so I picked up an older 320gb HDD I had unused, changed it, and tried to restore. Only to find this ridiculous requirement. Now I’m forced to install it all over again. And I won’t trust MS builtin tools for backup anymore. And I was thinking that Windows finally was “good enough” with the 8th version….
More links on the subject: windows 8 the system image restore failed disk too small. Some people listed work-arounds for Windows 2008 server. Not worth to a desktop.
cya! And take your backups with something else!
Just saw this while watching (a part of) MVA Jump Start: Querying SQL Server 2012: Logical Query Processing Order. This is great to keep in mind while tuning your queries.
As I was blogging around and found this content on a follower, I decided to share it here too.