Top posts
Latest articles
Migration to MS SQL 2005 nearly completed
(No Ratings Yet)
Loading ...As you all might have noticed in the posts of the past few weeks we’ve been migrating from SQL Server 2000 to 2005. Well I’m happy to say that were almost done. And that after only two weeks.
A you may have read in the day after post the physical migration went al right. It was after migration we encountered some problems. I’ll give a short list of all the problems:
- When running multiple SSIS packages at once the server breaks, our packages that take a bit longer fail reporting that InnerPackage.dtsx is locked by the OS.
- The SQL server likes to allocate more memory in the physical memory the actually present, causing it to crash (can be fixed by setting a memory limit)
I’ve reduced the first problem by reducing the amount off time needed to execute the single SSIS packages.
Slow progress
Hi you all. I’m afraid that for the next couple of weeks there will be less new posts then before. This all because I have broken my wrist last Wednesday.
I’ll still write every no and then, but it’s all going a lot slower with one hand. At least a lot slower then I am used to.
That’s it for now, until next time…
Day 1 after the migration
As you may have noticed in my last entry I’ve migrated our database system from SQL Server 2000 to a new physical server and to MS SQL 2005. And as usual no matter how well you test something always goes wrong.
Everything started out ok yesterday, sure we killed the website by trying to place a constraint in place for the migration. But those are just minor details 
. To be honest I only had one problem during the entire migration and that was during the restoring of an internal database, so nothing critical.
It was strange however, that after performing a restore the database did not come out of the RESTORING state. Googled a bit, found out that it is a known issue when you use the WITH NO RECOVERY option. So restored it again without that and it worked fine.
Unfortunately the real problems always have a way of showing themselves after you go home. Preferably in the middle of the night. And last night was no different. At midnight (ECT) our live database server crashed. Apparently MS SQL 2005 has a known tendency to ask more memory then physically available on the server, at least if you don’t set a constraint on the server. And just to make live even more complicated our CUBE processing failed and we had 3 issues with a payment service provider.
I really hate Fridays…….
Working the graveyard shift
Today for the first day in a long time I’m working on the graveyard shift. Well it will probably be the only time. This all because of a major migration of our database systems.
Well I gotta say, I like it. It’s nice and quiet in the office and on the streets.
Avoiding Visual Studio 2005 for C++
Ever since I rewrote my ‘Synch’ tool I got some complaints from people that they could no longer run it. All they got was a cryptic message ‘Unable to execute file’.
At first I thought they were just missing the C++ runtime libraries, so I gave them the advice them to install the Visual C++ 8.0 runtime. But they still reported the same problem. So I started enquiring a bit of more background information on their systems.
After some research I found out that only system that did not have the .Net runtime version 2 installed gave this error. But this was strange since the program was native C++. I hadn’t used any .Net classes or libraries. I even compiled it with the option ‘Windows libraries only’.
It took me quite a bit of time to finally figure out that the bastards at Microsoft compile with .Net support by default. So if you include the AFX libraries (which is what I did for some API calls) .Net is automatically included for some reason. I only had the problem with this version since I switched from Visual Studio 2003 to Visual Studio 2005.
And sure after I reverted all projects to Visual Studio 2003 and gave the new program to the people that reported the problem they were able to run it again. So in short Visual Studio 2005 is great for people not developing C++ code.
Using visual studio 2005 means you are bound to include .Net libraries with all your projects, which is something I don’t want for basic console applications!!!! Guess I will be sticking with 2003 for the next couple of decades.
