Upgrading to SQL Server 2005

The date the for SQL Server 2005 release is closing up. If everything goes as planned it will be the 10th of Novemeber.

I'm just curious about who are planning to upgrade and who will not.

Personallt, I'm not sure what to do. We have a huge internally developed application used for engineering, document control and planning that is currently replicated to 8 sites acrosss the world.

I will have to do extensive testing before I do any upgrades, but I must say that if everything turs out weel I will certanly upgrade. There is so much functionallity in SQL Server 2005 that I would like to have that I hope the testing goes well, and I can go along with the upgrade.

I would be fun to see who are planning to do upgrader, or perhaps change from another RDBMS to SQL Server 2005.

It would also be nice to know the reason why you answer as you do.

None of the poll answers match what we are going to do - which is see what effect the new release has on our existing products lines.

I would expect it to be 100% compatible - so I should see no damage in the 2000+ stored procedures and user defined functions we have...

But that's going to take some time to research.

I've got one customer who probably wants to install it 2 months after it's released. I've got another customer who would probably wait two years to install it.

I'm stuck in the middle...

Quote:

---

Originally Posted by szlamany

None of the poll answers match what we are going to do - which is see what effect the new release has on our existing products lines.

I've got one customer who probably wants to install it 2 months after it's released. I've got another customer who would probably wait two years to install it.

I'm stuck in the middle...

---

Unfortunately I cannot change the poll questions. I will try to keep a count of answers that doesn't match any of the answer alternatives instead.

Am I correct if I say that you would give your vote to alternative no. 5 (new):

5: I will wait with the upgrade until I know more about what extra benefits and functionallity SQL Server 2005 gives me.

With that as the 5th choice, I would have to lean towards the first choice - I am going to convert - it's a matter of my customers following. I cannot force them - but most will want to anyway.

Quote:

---

Originally Posted by szlamany

With that as the 5th choice, I would have to lean towards the first choice - I am going to convert - it's a matter of my customers following. I cannot force them - but most will want to anyway.

---

Well, I'ts hard to give goods options for everybody ;)

I'm esåecially excited how the tight .Net integration will turn out. They also promised row level security, but I know for a fact that that has been cancelled due to performance issueds.

Ok - I've seen 24 views of this thread - but only 2 votes...

Anyone have an opinion on this??

Well I'm not actually working at the moment (between jobs!), but at my previous job the answer would have been:

Wait for a while before considering it - many pieces of software have issues when they are released, the company policy is to wait for at least one service pack (or the next version to be released if sooner!) before using a particular piece of software, unless it fulfils a specific urgent need.

To start with, any new databases would have the option of using it (after a 'proving' period it would become mandatory for all new ones). For any existing databases, they would not be allowed to move until other databases have proved the validity of the new software (in terms of reliability & compatiablility etc).

As such, my answer would be a mix of the 2nd and 3rd options, but mainly 2.

Quote:

---

Originally Posted by kaffenils

Unfortunately I cannot change the poll questions.

---

I can, but what would we change them to?