Hi - I have an MSDE database running on my server - I'd like to port my asp.net 1.1 app to asp.net2, and make use of SQL 2005 Express.
How do I transfer my data from an MSDE database to SQL Server Express, keeping intact all of my unique ID fields, indexes, and SPs (I don't have any functions or views)
Thanks for any help,
Mark
I posted previously about concerns of using SQL Server 2005 Express in a shared hosting environment that is running SQL Server 2000. While I've received no responses I'm beginning to assume that an .mdf file created by mssql 2005 cannot be attached to mssql 2000. So I have a few questions...How do I set Visual Studio to create the aspnetdb file using an instance of msde instead of sql server express 2005? I've already tried changing the Instance name under Tools...Options...Database Tools...Data Connections to my msde instance but when I create a new site and use the the website configuration tool a sql 2005 db is still created in the App_Data folder.Do I need to uninstall 2005 express? Manually create and place a new .mdf file in the App_Data folder?
View 1 Replies View RelatedI have heard that machines running applications with embedded MSDEfrequently experience conflicts between the MSDE apps and otherapplications such as BackupExec. What can anyone tell me about this?And if this is true, does/will the new SQL Server Express Editionbehave better?
View 1 Replies View RelatedWe are attempting to backup using a maintenance plan a database to a network share.
The backup job works within a domain but fails within a workgroup?
Any thoughts?
thanks
I have an application that is already installed on a Win2k3 Server using SQL Express 2005. I have another application that wants to use MSDE 2000 (already tried using SQL Express 2005, but it won't install). My question is, can both of these be installed on the same server and running at the same time without any problems? Thanks!
- Adam
Hi - is it possible to migrate to SQL Server 2005 Express from MSDE - and still use ASP.Net 1.1? Or will Express only work with ASP.Net 2.0?My MSDE database has simple SPs (no functions), and straight forward tables - can I just use DTS from Enterprise Manager to transfer this from MSDE to SQL Express, or create a backup, and import that into SQL Express 2005?Also, there was a sort of Enterprise Manager available for SQL Server 2005 Express at one point - does anyone know where to find that?Thanks for any pointers/help.Mark
View 4 Replies View RelatedHi guys,
I'm just wondering if the MSDE & SQL Server 2005 Express can run on the same machine(winxp) without conflicts. Because I need both the reporting services & the publication functionality of replication.
Thanks in advance.
I read in the installation requirements document for SQL Server 2005 Express the section on upgrading MSDE to SQL Server 2005 Express. The section indicated that if MSDE is installed via an application installation, that application will have to be uninstalled to remove MSDE. This leads to my question.
The small application I'm looking into developing will require SQL Server 2005 Express. What if a customer is using an application that installed MSDE? Can the two products coexist without problems?
Thanks!!
Hello,
at the moment I have the following problem:
We have installed a version of the MSDE 2000 Sp3 with our software since 2005. Now we install SQL Server Express 2005 in order to use the latest version and to be compatible with Vista.
We have never had any problems with the MSDE, so it was no problem that we installed the german version (by mistake) because there never was any output at installation time.
When we now upgrade the existing MSDE installing the new version of our software, there are often problems and there are error messages, unfortunately in german, which cannot be read by most of our international users.
The problem is, that there seems to be no possibility to upgrade the existing (german) MSDE with the english version of SQL Server Express 2005.
My question is, if it is possible to upgrade the german MSDE to the english SQL Server 2005 to enable our international users to read the error messages at installation time in english?
Thanks in advance.
Best regards,
Peter
has anybody tried to do that yet? any experiences? how-tos?
View 3 Replies View RelatedHi,
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install.
MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used.
When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ...
sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.
sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process.
sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Error Code: 15119
MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'.
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement:
/**************************************************************/
/* Sign agent sps and ...
Script file: sqlagent90_msdb_upgrade.sql
The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x80073b0f (15119)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967
Source Line Number: 91
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
Thanks and Regards,
Sahil Girotra
Hi,
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €ś[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues.
2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
Thanks in Advance.
Regards,
Sahil Girotra
I have a Windows Server 2000/Windows Server 2003 Environments with MSDE installed (default instance) and SecurityMode is SQL. I want to upgrade from MSDE to SQL Server 2005 Express Edition using a silent install since the number of servers is huge.
I downloaded the latest SQL Server 2005 Express Edition SP2 Version 9.0.3042.0 from http://msdn2.microsoft.com/en-us/express/bb410792.aspx
I am having the following problems:
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting SQL authentication, the install fails with an error "SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade".
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting Windows authentication, the install fails with an error "Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>
I had earlier tested upgrading the MSDE installation to SQL Server 2005 Express Edition Version 9.00.1399.6 downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en and the upgrade worked successfully using SQL Authentication (SA User and corresponding password), but for some reason it doesn't work when I use the latest version 9.0.3042.0.
Has anyone else faced similar issues. Any tips on how I can upgrade from MSDE to SQL Server 2005 Express Edition SP2 are welcome.
Thanks in Advance.
Sahil Girotra
Hi,
View 5 Replies View RelatedI have a database on one server that is running MSDE and I would like to copy it to another server running SQL Server Express.
The process I followed was to create a backup on the first server.
Copy the backup file to the other sever
Then restore using the backed database file on the new server
Is this the right procedure? Everything I see about migrating in on the same server. I do not want to do it on the same server as we are migrating the application to the new server.
Can anybody help?
I have a Windows XP and 2003 server; we have installed SQL 2005 Express on it but have an application that installs MSDE 2000 to connect to an application. After the MSDE 2000 is installed we can no longer see the instance across the network. If we uninstall the SQL 2005 express version we can see the Instance in MSDE 2000.
Is there any compatibility issue with install MSDE 2000 after SQL 2005 has been installed.
Many Thanks in advance
David
hi - I am developing locally using .Net 2.0/Access but just recently started trying out SQL Server Express. I have deployed my application to a host who provides 2.0 but as would be expected only MSDE/SQL server 2000. Now if I'd switch completely to SSE, would my SQL queries (which are pretty simple) work on MSDE or SQL server 2000? The only thing I see as more sophisticated sql queries would be the built-in 2.0 Roles/Membership functions... Do you think they would run smoothly on MSDE/SQL 2000?Finally... since the database is already done locally, is there any way (a stored procedure for example) to copy it's scheme if I'd create a new DB on my host's SQL server?
View 2 Replies View RelatedHello guys! I have to develop a new web based project. It's a web
portal for events. At the moment it's runnung on an Access database.
The new version should be running on a SQL server - the desicion is:
MSDE 2000 or SQL Server 2005 Express (Beta). What do you recommend? The
webpages are developed under .NET 1.1.
Hi, I'm wondering if I can use SQL 2005 Reporting Services with SQL Server 2000, SQL Express or MSDE, or I need to install SQL Server 2005 in order to use Reporting Services 2005? Thank you in advance.
Regards,
Miguel
I'm trying to attach a MSDE 2000 database to SQL Server 2005 Express.
I simply issue sp_detach_db XXX where XXX is the name of my MSDE database. Then sp_attach_db or create database ... with attach and both way gets the following message:
Event ID. : 3415
Description: Database 'XXX' cannot be upgraded because it is
read-only or has read-only files. Make the database or files writeable, and
rerun recovery.
What does it mean?
Thanks for any help,
Peter
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
Thanks for any help.
I am trying to do a unattended upgrade of an MSDE 2000 named instance, say MyInstance, to a SQl Server Express Advanced edition. The set up is Mixed Mode Authentication. ( I can't use Windows Authentication for business reasons).
The error I get is
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Creditial. You must use Windows Authentication creditial for the upgrade.
Details are as follows:
OS: Windows XP Prof (SP2).
Original install: MSDE 2000
Instance name: MyInstance
Authentication: SQL
Registry Entry: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMyInstanceMSSQLServer
Key LoginMode has a value of 2 ( corresponding to Mixed Mode Auth)
Upgrade attempted to: SQL Server Express Adv.
Command Line: start /wait setup.exe /qn LOGNAME=C:setup.cab /settings E:Sql2005SqlTemplate.ini
SqlTemplate.ini Contents:
[OPTIONS]
INSTANCENAME=MyInstance
SECURITYMODE=SQL
UPGRADE=SQL_Engine
UPGRADEUSER=sa
UPGRADEPWD=My$Password
The error I get in Summary.txt:
Machine : xxxxxXP
Product : SQL Server Database Services
Error : SQL Server Setup cannot upgrade the specified instance by using SQL Server credentials. You must use Windows Authentication credentials for the upgrade.
Can't I use SQL Authentication? I could not find a definitive answer on this one. Here's one thread that seem to indicate the same issue
http://groups.google.com/group/microsoft.public.sqlserver.msde/browse_thread/thread/90fb4b7182a55d54/f3128b447585f29d%23f3128b447585f29d
My questions:
- Can I use SQL Authentication?
- Where am I going wrong?
- I know the error message says to use Windows Authentication but I don't understand why I am I forced into using that.
Any insightsopinions will be highly appreciated. I am on the verge of a breakdown :(.
Best
LW.
I am trying to do a unattended upgrade of an MSDE 2000 named instance, say MyInstance, to a SQl Server Express Advanced edition. The set up is Mixed Mode Authentication. ( I can't use Windows Authentication for business reasons).
The error I get is
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server
Creditial. You must use Windows Authentication creditial for the upgrade.
Details are as follows:
OS: Windows XP Prof (SP2).
Original install: MSDE 2000
Instance name: MyInstance
Authentication: SQL
Registry Entry: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMyInstanceMSSQLServer
Key LoginMode has a value of 2 ( corresponding to Mixed Mode Auth)
Upgrade attempted to: SQL Server Express Adv.
Command Line: start /wait setup.exe /qn LOGNAME=C:setup.cab /settings E:Sql2005SqlTemplate.ini
SqlTemplate.ini Contents:
[OPTIONS]
INSTANCENAME=MyInstance
SECURITYMODE=SQL
UPGRADE=SQL_Engine
UPGRADEUSER=sa
UPGRADEPWD=My$Password
The error I get in Summary.txt:
Machine : xxxxxXP
Product : SQL Server Database Services
Error : SQL Server Setup cannot upgrade the specified instance by using SQL Server credentials. You must use Windows Authentication credentials for the upgrade.
Can't I use SQL Authentication? I could not find a definitive answer on this one. Here's one thread that seem to indicate the same issue
http://groups.google.com/group/microsoft.public.sqlserver.msde/browse_thread/thread/90fb4b7182a55d54/f3128b447585f29d%23f3128b447585f29d
My questions:
- Can I use SQL Authentication?
- Where am I going wrong?
- I know the error message says to use Windows Authentication but I don't understand why I am I forced into using that.
Any insightsopinions will be highly appreciated.
Best
LW.
Are there any concerns for upgrading from MSDE to Express? Anything that has to be done to the database itself?
I will be uninstalling MSDE completely so I can reuse the instance name to minimize issues with other programs already setup for it. This means that I will be installing Express, basically, clean on the machine. What I am worried about is anything that needs to happen to the db itself, changing compatability levels and such.
Thank you in advance for any help.
Hi ....I am a developer and building an enterprise level application for general purpose. I need to include a database in that. I am working in Visual Studio .NET 2003 having Framwork 1.1 installed. Now what should I do? is it necessary to have visual studio .NET 2005 and Framwork 2.0 to work with SQL Server Express? can any one help?
Amir
I know this may have been asked in the past, and I've tried to search the forum, but didn't find any clear responses.
The question is about MSDE and SQL Express being "Free".
Can MSDE or SQL Server express be used for the backend DB for an application for a private (for profit) company? A COTS that we are planning to puchase can work with either commercial version of SQL server or MSDE / Express. Any input would be appreciated.
Thank you,
We have a product on the market, with 100k or so installs that use MSDE as its database (desktop application in .net). Our number 1 complaint is massive installation problems with MSDE.
Now, we are stuck a bit - first, we need to release a Vista Compatible version - which means no MSDE. We also need to migrate users from MSDE to SQL Express, with no data loss (we deal with financial information, and people tend to have zero tolerance for data loss here).
So, I have large scale reservations for two reasons - first, Microsoft's track record in supporting and making MSDE in the past has not been stellar.
With that said - are the multiple installation failure issues fixed in SQL Express? Did MS make the effort to get SQL Express to install on Win2k/XP/Vista improved? Are their benchmark figures out there regarding SQL Express install failure rates?
Additionally, can I get some information regarding MSDE to SQL Express upgrades done during for existing customers?
jason
I need to know if I will run into problems with sql express on a sql 2000 server. I get the impression that my isp is using 200 server just by lookng at the connection string. Is there a addin I could use if needed I seen a post mentioning the publishing wizard cpt but not much after is it released yet. and then there is the web data admnistrator for msde will that work with sql express.One other question can I reinstall sql and change the authentication process from windows to user name and password.
DKB
Not sure where to poswt this but I have a question. Is it possible to downgrade a remote SQL instance (the RTC database for LCS 2005 EE) to MSDE / SQL EXPRESS running on the LCS node?
I have two LCS2005EE pools side by side in the same account domain. The company recently went through a split where a part of our operation was spun off to another company. We're trying to figure out a way to leave them a working LCS but cut our hosted server count. What I came up with was basically 3 or 4 possible scenarios:
Leave only two servers (LCS and SQL.)
Try to move and run two instances on new production equipment
Try to downgrade the remote RTC instance into MSDE / SQL EXPRESS and leave one server.
Any ideas would be greatly appreciated.
Joe H. Wise
Hi everyone!
We are trying to restore a database backup created o MSDE 2000 server to SQL Express 2005.
The collation settings of both SQL Express and MSDE are the same: Turkish_CI_AS
The problem is that the log of restore operation has some warnings like:
Processed 344 pages for database 'MYDB', file 'MYDB_Data' on file 1.
Processed 1 pages for database 'MYDB', file 'MYDB_Log' on file 1.
Converting database 'MYDB' from version 539 to the current version 611.
Database 'MYDB' running the upgrade step from version 539 to version 551.
Warning: The index "myt_idx01" on "dbo"."myt" may be impacted by the
collation upgrade. Run DBCC CHECKTABLE.
Warning: The index "PK_BankLDef" on
"dbo"."BankLDef" may be impacted by the collation
upgrade. Run DBCC CHECKTABLE.
Warning: The index "AgreeHist_idx1" on
"dbo"."AgreeHist" may be impacted by the collation upgrade.
Run DBCC CHECKTABLE.
....
....
Database 'MYDB' running the upgrade step from version 551 to version 552.
Database 'MYDB' running the upgrade step from version 552 to version 553.
Database 'MYDB' running the upgrade step from version 553 to version 554.
Database 'MYDB' running the upgrade step from version 554 to version 589.
Database 'MYDB' running the upgrade step from version 589 to version 590.
Database 'MYDB' running the upgrade step from version 590 to version 593.
Database 'MYDB' running the upgrade step from version 593 to version 597.
Database 'MYDB' running the upgrade step from version 597 to version 604.
Database 'MYDB' running the upgrade step from version 604 to version 605.
Database 'MYDB' running the upgrade step from version 605 to version 606.
Database 'MYDB' running the upgrade step from version 606 to version 607.
Database 'MYDB' running the upgrade step from version 607 to version 608.
Database 'MYDB' running the upgrade step from version 608 to version 609.
Database 'MYDB' running the upgrade step from version 609 to version 610.
Database 'MYDB' running the upgrade step from version 610 to version 611.
RESTORE DATABASE successfully processed 345 pages in 0.420 seconds
(6.712 MB/sec).
What is the severity of this warnings? Is there a way to make them disappear?
Thanks in Advance.
Adnan
I posted this in one of the VB forums but I'm starting to think itmight be more appropriate to have it here, since it really seems to bea SQL server (MSDE/Express 2005) problem:Hey, all, I have a problem with queries against a SQL server instancethat I just found and is causing me fits. I hope someone can pointmein the right direction, please. TIA.Basically, I got a Vista OS machine to test my VB6 app on it as someof my clients will be switching over in the coming months. I went toa local Circuit City during early business hours in the middle of theweek and I installed my application on each of 5 PC's on the newVistaOS (Tuesday, when it was released). I had read that MSDE 2000, whichI normally use as my DB is not supported on Vista so I had downloadedand was using SQL Express 2005. Each system had at least a 1.9 GHzdual core processor and 1 GB of RAM. One process in my program findsrecords in one table that do not match records in another table andthen reports those un-matched entries. On my development machine(laptop with 1 GB of RAM, XP Pro SP2, MSDE 2000 (current SP), 2 GHzCentrino (IIRC)) the process takes less than 30 seconds consistently.On each of those 5 systems at Circuit City the process took 5 minutes(on each of 3 HP machines, a1700n, a1720n, a1730n, and 11 minutes oneach of two Gateway systems (the model numbers of which I forget atthe moment). Each of these computers should be much faster than mylaptop, and some had twice the RAM, and all had SATA or SATA IIdrivesinstead of my piddly 5400 laptop drive, I would have thought they'dall be faster but were abysmally slow.So, seeing a huge difference in the time, and to try to keep thisshort and sweet, I fired up another computer I have, running XP SP2,on 512 MB RAM, AMD Athlon 2300+. First I loaded MSDE 2000 and myapplication and ran the process. < 30 seconds on each of multipleruns. Second, I unloaded MSDE 2000 and installed SQL Express 2005andmoved the DB to it (sp_attach_db) which caused some upgrading(messages reported in OSQL about update/upgrade). When it was done Irebooted, to be sure, and the ran the program and the process again.On the same data, on the same computer, the process took 7-9 minutesconsistently on each of several runs. This makes this part of theapplication unusable, and even the simple stuff like grabbing asinglerecord from the DB (maybe 5 columns of no more than 500 bytes total)is noticeably slower on the SQL Express 2005 than on MSDE 2000.So, the problem seems to be with my interaction with the DB. I amusing ADO 2.8 in VB 6 (SP 6). I use DSN-less connections with aconnection string like: Driver={SQL Server};server=(local)caredata;database=caredata;Uid=sa; Pwd=<password>I use the RecordsSet Object to open the data similar to this:oRS.OpenstrSQL$, oCN, adOpenKeysetafter the oCN object has had the connection string set and the objectis opened.Considering that the same computer, against the same data, with thesame program, takes about 14 times (or more) longer to run, then ithas to be either that SQL Express 2005 is slow OR that my program isinteracting with it in an incorrect manner.Can someone point me in the right direction, please?Thank you.--HCSo, the problem isn't Vista
View 11 Replies View RelatedI have a 3 workstation peer to peer network with everything running Windows XP Pro. I need to replace the machine that hosts my SQL MSDE server. I have built a new system and all software is installed except the MSDE. I use a proprietary product called Time Matters for my law practice that uses the SQL server. Since I might want to run Vista eventually (not right now) I thought that I would try to migrate the MSDE to SQL Express. I assume that Time Matters will run on SQL Express. Can someone please give me some help on how to proceed. I'm thinking that I will install the SQL Express server on the new machine and then somehow migrate the database over to the new machine and shut down the old unit. Any help would be greatly appreciated.
Is the installation of MSDE and SQL Express 2005 on the same computer a supported configuration?
Many thanks