Actually, you don't need NT. The SQL Enterprise Manager will run in Win 95/98. Just pop the SQL Server CD into your machine and run the install. The only option available to you will be to install the Client Utilities, which include the Enterprise Manager. Of course this assumes you have SQL Server running somewhere on the network! If not, then as John said, you'll need NT.
My only other recommendation is to pay very close attention to how the Upsizing Wizard creates your indexes in SQL Server. When we used it it changed the field order of the indexes. Field order in indexes is VERY important in SQL Server. The SQL Server query optimizer looks at the WHERE clause of your select statement and looks for an index with the same field order as the conditions in your query. Our performance went right down the toilet until we discovered the index problem.
Have fun!
>Allright! now I'm encouraged :)
>
>>Hi Larry ---
>>
>>1) Run NT on your machine so you can get to SQL Enterprise Manager.
>>2) Have the latest version of SQL Server ODBC drivers.
>>3) Ridalin helps...if not that, then Valium or at least Scotch.
>>
>>Good luck!
>>
>>>What kinds of things must be in place in an application to facilitate the upsizing wizard and make the transition from local .dbfs to SQL as "painless" as possible?
>>>
>>>TIA
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
