Software

Ask something
Discussion Locked

W2K server and SQL2K support

0 helpful
6 replies

by jep

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have developed an application in NT4 server and SQL7. We are now customizing this application for a new client, which we have been doing for several months already. Then just yesterday, I received the information that client's IT manager has required that our application must run on W2K server and SQL2K. This was not in any of our previous discussions and only came out now. My question now is what is the best approach to handle this problem in case client's IT manager insists on their requirement? In this case, I plan to request for an extended schedule, but my concern is that already many departments in client's company expect system to be ready end of Sept. To port an application from NT4/SQL7 to W2K/SQL2K, how long would we need to test before we can be confident it is stable (the DB part is subcontracted, I need an independent opinion)? Thanks for any reply.

6 replies

by jb007

Every project manager has a set of "concrete" rules that should be followed to minimise the issues that may arise during a project.

Its the adherence to the "scope" of the project (in this case writing the app on a certain platform BY a certain time) that stops the project from going overtime and potentially not meeting its original goals (project creep).

Amongst these are usually definitions for:

a) timeframes (how long?)
b) resources (who's involved?)
c) cost (how much can i spend?)
d) contact (people to advise to make critical decisions in case of problems)

the list is virtually endless.

What i do know though is any consultancy will create an outline and will NOT (if they have any intelligence at all) deviate from a project plan unless they are forced to by the client or important circumstances.

Your case... you have completed your project and the porting to w2k and sql2k should be a totally different project.

Use the knowledge gained from the previous project.. if anything at all it would only make the planning of the second project faster and easier to implement.

hope this helps,

btw take a look at a few easy project management books you can never know enough.

cheers,

jb

by glen_mcleod

Regarding the database: anything that runs in SQL Server 7.0 will run in SQL Server 2K, the things that will need to be tested is the surrounding applications, and then only for certain Windows components that may have changed between NT4 and 2K. All of the stored procedures, views, DRI, security, schema, etc. that you wrote for 7.0 will work just fine in 2K. Of course, you won't be taking advantage of any of the new features in 2K like UDF's or the new data types, but that shouldn't be your primary concern at this point.

Glen

This discussion is closed to new replies.