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.
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.
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.
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?
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.
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?
Hi, I am working on a test installation of SQL 2K5 but I need to copy a D.B. from SQL 2K5 to a SQL 2K. I tried with backup but the restore in SQL 2K does not work, anyone can help me?
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.
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
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.
I'm experiencing problem here that we need to downgrade our sql 2005 back to version 7.0.
Apparently, all the mdf files from 2005 are recognized as "corrupted" by the 7.0 server. All my dbs are created within 2005 and i'd like to move these to the older 7.0 server.
I wonder whether there are any procedure to convert 2005 mdf files so that is is compatible with sql server 7.0? or what is the most common way of solving this? Any pointer would be appreciated. thx!
Hello, my question is simple, i guess, if anyone can help me solve this problem: I just installed Windows 2003 SBS Premium R2 but i have a software using SQL Server 2000 and not the one included in this version, 2005 wich is not compatible with. How can i downgrade, where cand i get the older server if the downgrade is possible and what else can i do before i shoot myself? Is there any license issue that will not allow me the downgrade? Thank You!!!
We have hit performance issues with our SQL server after upgraded it to SP3 from SP3a, is there any way that I can downgrade it back to Service Pack3a??
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?
I 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?
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
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!
I 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.
Hi all,I was running an MSDN version of SQL 2000 Developer Edition on a serveruntil I accidentally upgraded it to Enterprise Edition while attemptingto install some Management Tools. Is it possible to downgrade it backto Dev Edition?Thanks,Josh
I have developed a database using SQL Server 2005 Express for 2005 Enterprise. My client now realises they don't have a licence for 2005 and require a copy of the database that will work on SQL Server 2000. I can find plenty of information about migrating from 2000 to 2005 but not the other way round. Is this possible and, if so, I would really appreciate any pointers on how to do it. Patrick Grey
We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:
1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.
2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).
3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).
4. Apply sp4.
5. Restore user databases.
Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.
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
Hi; In http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=71679 topic, it is stated that SQL-DMO can be used to make msde publisher for transactional replication. But in http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=71983 topic, Rishi said that "No Express Edition cant act as Publisher". I am not clear about the difference btw msde and express. Why msde can be publisher for transactional replication by SQL-DMO and why express edition can not be? Thank you so much...
I wanted to to detach a DB say MyDB from MSDE and wanted to attach it to SQL Express. It could able to Detach the DB from MSDE,but attachment to SQL 2005 is failing. When I verified MSDE Instance through Managment studio "MyDB" wasnot there ; means it got detached.I couldnt find the DB in SQL 2005. When I tried manually through command prompt I was able to attach "MyDB" to SQL2005. Please help me out!! Here is the code which I have written.
if SUCCEEDED(hr = CoCreateInstance (CLSID_SQLDMOServer, NULL, CLSCTX_INPROC_SERVER, IID_ISQLDMOServer, (LPVOID*)&pSQLServer)) {
pSQLServer->SetLoginSecure (TRUE); SQLDMO_LPCSTR DB = OLESTR("MyDB"); //Connect to MSDE First if SUCCEEDED(hr = pSQLServer->Connect (szDbServer, szUserName, szPassword)) {
pSQLServer->DetachDB(DB,lpszResult); //Detach the DB pSQLServer->DisConnect(); //Disconnect MSDE LPBSTR lpszResult2 = NULL; long lNumDB; //Connect to SQL 2005 if SUCCEEDED(hr = pSQLServer->Connect (szSQLExpDbServer, szUserName, szPassword)) { //LPCOLESTR lpo = A2COLE(sTemp); //sTemp.operator LPCTSTR pSQLServer->GetDatabaseCount (&lNumDB); SQLDMO_LPCSTR files = OLESTR("C:\Program Files\Microsoft SQL Server\MSSQLData\MyDB.mdf,C:\Program Files\Microsoft SQL Server\MSSQL\Data\MyDB_log.ldf"); pSQLServer->AttachDB(DB,files,lpszResult2); // Attach the DB to SQL 2005
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.
I have 2 MSDE 2000 Instances installed on Windows 2003 Server STd w/ SP1.
The application relating to the default instance is being upgraded and will require SQL 2005 Express.
What is the best approach? So the named instance of MSDE 2000 still functions correctly.
Upgrade default instance of MSDE to SQL 2005, or install SQL 2005 Express to own path and restore the DB accross? Then remove the Default Instance of MSDE 2000.
Both MSDE 2000 Instances are listed in Add/Remove Programs.
I have been testing one of our Apps under SQL 2005 Express and I am seeing a big downgrade in performance compared to MSDE on the same hardware. Has anyone else experienced this?
Currently I am running MSDE on a webserver. The MSDE was installed by a software package for web survey's. I am wondering if SQL express will interfere with this installation? Would I be better to install MySQL instead?
The problem I am trying to solve is simply giving a web developer some database space so that he can connect his web app to store some data. I'm kind of a n00b at this so I thought SQL express would be the best route. If I'm headed in the wrong direction can someone point me the right way?
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?
Hi I would like to ask If its possible to have installed MSDE 2000 and SQL 2005 Express on the same machine. My computer uses MSDE 2000 for one application and I would like to install SQL 2005 Express for my own application. I would like to ask it will be a problem before I install it. thanks a lot Martin Molnar
I have just done an in-place upgrade from MSDE to SQL Express with Advance Services for my customer. After upgrading, the program was not enable to connect to SQL Express and threw an error (the program connect to the server through OLEDB provider)
Code -2147217843 (80040e4d) - IDispatch error #3149 - Source : Microsoft OLE DB Provider for SQL Server
It only works if I replace the string "Provider=SQLOLEDB.1" with "Provider=SQLNCLI.1". I wonder why I have to do that because in my working PC and other customers, I don't get this.
The customer's PC use Windows 2003 Server for Small Business Server SP1
