Showing posts with label desktop. Show all posts
Showing posts with label desktop. Show all posts

Friday, March 23, 2012

Migrate subset of data from 2000 to 2005

First a little background.

Production server is SQL Server 2000. Various clients will be installing a desktop version of our web application. The desktop app will be running SQL Server 2005 Express (MSDE replacement, correct?). When the client downloads the package, the installer will import their data from the SQL Server 2000 production database into the SQL Server 2005 database. The production database contains numerous clients, so it doesn't make sense to migrate ALL of the data, only the data that belongs to the client.

My question is what method(s) would allow this to be done? The databases will NOT be connected to one another so using DTS packages is not an option.

After doing some research I came to the conclusion that the only way I could see this working, would be to output each tables data (just the data that belongs to the particular client) into its own text file and then import them individually on the SQL Server 2005 side.

Does anyone have any other ideas?

Kevin - I have the same dilemma currently and wondered if you had found a solution to this?

Friday, February 24, 2012

Microsoft SqlServer Desktop Engine Connection Problem

i installed the MSDE2000A on server and i tried to connect from client machine through vb Application using connection string. Server anad client are in LAN. but Some systems able to connect and some systems are unable to connect.

i am getting the error:

"SqlServer does not exist or access denied "

for non connected machines.

the server is listening from these machines. but not connecting to MSDE.

can anyone give me solution what may be the cause.Ensure the System DSN used and login must have required privileges to connect to SQL server.

What is the authentication mode used?

Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name

Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||i am using user authentication mode.
i have set DISABLENETWORKPROTOCOLS=0
i have done pinging through IP Address.
i am able ping database.
after doing all these test .. still getting same error...

is there any other possibilities....

Originally posted by Satya
Ensure the System DSN used and login must have required privileges to connect to SQL server.

What is the authentication mode used?

Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name

Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||Review points listed in the knowledgebase article.

i am using user authentication mode.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?

i have set DISABLENETWORKPROTOCOLS=0
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
i am able ping database.
How can you do that in SQL?|||mine is MIXEDMODE.

this is obtained by setting parameter SECURITYMODE=SQL

i am sorry to tell u that i ping to database.

not database... it is server.

i am able to ping to server where i installed MSDE.

Originally posted by Satya
Review points listed in the knowledgebase article.

SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?

Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.

How can you do that in SQL?|||I'm probably being silly, but could you have installed SQL as a named server and tried to access it as a default (unnamed) server?

-PatP|||Check for any h/w issues on server installed by referring to event viewer log.