SQL server Personal Edition

[StanKorn]

Hi, I'm trying to create an sql environment on my office PC whiuch is connected to a server. I want to learn SQL access issues before I start the actual system on an SQL 2K server. I have received a Personal SQL disk with the main system disk and am curious if this will resolve my immediate problem? I can also download SQL desktop from the net - Is this a better solution?
How difficult will it then be to sign on to the SQL instance? I need to bring some data over that is residing in a Visual Fox Pro environment and teach myself the import export routines and the analysis capabilities.
Any help would be greatly appreciated,
stan


Remember - only dead fish go with the flow.

 

[SQLRickster]

By Personal edition I take it to mean MSDE, which is SQL Server with a few governers. If you already have Enterprise Mananger and Query Analyizer installed locally, then it is a matter of registering the local instance in a SQL Server Group once MSDE is installed. To register the local instance simply open EM Right click SQL Server Group And follow the steps provided by the registration wizard. When asked to enter the SQL Server Name, type in the name of the instance and you should be all set.

If you do not have EM or QA installed, Install them first. MSDE does not come with either of these tools (at least not in the 7.0 version) and you will need these tools to be able to import and export your dbf files.

Hope this helps.
SQLRickster

 

[ecobb]

Actually, SQL Server Personal Edition is a version that ships with SQL Server. It should be just what you need. It will install SQL Server, as well as the client tools (Query Analyzer and Enterprise Manager), and allow you create and manage database just like a full version of SQL Server. I have Personal Edition on my laptop and that's what I use to manage all of our SQL Servers.

Once you get it installed, you should be able to import from Visual Fox Pro pretty easily.

Hope This Helps!

Ecobb

"Alright Brain, you don't like me, and I don't like you. But lets just do this, and I can get back to killing you with beer." - Homer Simpson

 

[StanKorn]

Thanks for your help to both of you. Next question if I may impose on your expertise-

I am from a desktop environment (Access, VFP, DBF) etc. Now I want to transfer my VFP & MDB tables to a new SQL environment. Can either of you point me a good How To link on the steps I need to accomplish this? I have read all the BOL that came with both my SQL 2K and the personal addition but I don't seem to be making any headway.
Thanks again,
stan


Remember - only dead fish go with the flow.

 

[ecobb]

Create a new database on your SQL Server. In Enterprise Manager, right click on that database and select "All Tasks", then "Import Data". This will take you through a wizard that will connect to your databases and transfer them to SQL Server. It will transfer the tables and data, but you may want to go through them when it's finished and make sure the datatypes are correct and the primary keys are still set.

Hope This Helps!

Ecobb

"Alright Brain, you don't like me, and I don't like you. But lets just do this, and I can get back to killing you with beer." - Homer Simpson

 

[StanKorn]

Hi Ecobb,
Thanks for your help.
I have managed to transfer most tables from my VFP app. I am having a problem getting certain trnx tables to transfer. I get a DBTYPE_DATESTAMP error and a resulting data overflow which prohibits me from transferring the records. Unfortuneately it is a main trnx table that I need to analyze.
Any thoughts on this that you may have would be appreciated.
thanx,
stan


Remember - only dead fish go with the flow.

 

[ecobb]

You may want to check the data in the database and make sure a date hasn't accidentally been keyed wrong. I ran into something similar before upgrading Access and found a few dates that had the year as 5003 instead of 2003 (or some other goofy mistake).

Hope This Helps!

Ecobb

"Alright Brain, you don't like me, and I don't like you. But lets just do this, and I can get back to killing you with beer." - Homer Simpson

 

[StanKorn]

I tried that but the data is all OK. When I start up EM I get an error saying that DCOM is not istalled on this sytem and its absence is known to cause incompatibility issues...
What is SQL looking for and could this be a part of the problem?
I'm going to try the import again and actually write down the fasilure messages I get.
thanx for your help
stan


Remember - only dead fish go with the flow.

 

[StanKorn]

Oops - I spoke too soon.
THe dates are ok if after 12/31/1999. Prior to that they show up as 1899/nn/nn.
I ran a query and told the wizard to place the results in a VFP table that it should create (will it create a table?) and then I saved it and ran it. I get an error - the OCDB VFP Driver operator/operand mismatch.
The only operand I am using is the >= in the trnx date field of the original file. Do you have any thoughts?
Also I am using theMS VFP Driver for the source data. I have tried VFP Databases & VFP tables. What should I use as a destyination table for the results. Eventually I need to populate a Java app for my operation and I am attempting to ease the migration in January.
thanx,
stan


Remember - only dead fish go with the flow.