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,
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
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
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
View 4 Replies View RelatedNot 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 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 RelatedI 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 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
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.
Is the installation of MSDE and SQL Express 2005 on the same computer a supported configuration?
Many thanks
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;
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...
All,
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
pSQLServer->DisConnect(); // Disconnect SQL 2005}
Hi 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.
Hi,
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.
Thanks
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?
Cheers
Aussie Coder
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?
Cheers!
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!!
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
Thanks in advance
Huy Le
has anybody tried to do that yet? any experiences? how-tos?
View 3 Replies View RelatedJust wondering. On some workstations and a couple of servers we
have apps each running an instance of MSDE so these machines each have
anywhere between 2 - 5 instances of MSDE each.
Would it be benificial from a resources point of view (not to mention a
patching one) if we set up one instance of Express to replace the
multiple MSDE ones?
Anyone got any thoughts?
Antony
Hey, This is my first time posting here but here goes nothing...
Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.
BUT.
When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.
[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.
I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.
Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?
Thanks,
Hello, all, I started out thinking my problems were elsewhere but as Ihave worked through this I have isolated my problem, currently, as adifference between MSDE and SQL Express 2005 (I'll just call itExpress for simplicity).I have, to try to simplify things, put the exact same DB on twosystems, one running MSDE and one running Express. Both have 2 Ghzprocessors (one Intel, one AMD), both have a decent amount of RAM(Intel system has 1 GB, AMD system has 512 MB), and plenty of GB offree disk space. MSDE is running on the Intel system, Express isrunning on the AMD system. To keep things fair I use the exact sameDB's and query on both systems. The DB's were created on MSDE so Isp_detach_db'd them from MSDE and then sp_attach_db'd them to Express(this is how MS says to do a "side-by-side" upgrade, so it'sacceptable to do so). After fighting problems in performancedifferences in different situations I have narrowed the problem downto this:Executing a simple select statement with join clause on the databasesyields a difference in execution time that is quite great. Using theExpress Management program I can run the query against either system(MSDE or Express, the two systems are connected via crossover cable toeliminate any network problems/issues). When running the queryagainst the MSDE system (which is over the network) I consistently get<20 ms response times on the query. When running the query againstthe Express installation (which is in shared memory) I consistentlyget 700 ms or longer response times. Both times are for the TotalExecution Time.The query is simply this: select db1.* from db1.owner.tablename as db1inner join db2.owner.tablename as db2 on db1.pkey = db2.someid wheredb1.criteria = 3So, gimme all the columns from one table in one DB (local to theinstallation), matching the records in another DB (also local to theinstallation), where one field in the first db matches a field in thesecond db and where, in the first db, one column value = 3.The first table has a total record count of 630 records of which only12 match the where clause. The second table has a total record countof about 2,700 of which only 12 match up on the 12 out of 630.Even though the data is the same and I've done the detach and attach,and even done the sp_updatestats, the difference in execution time isremarkable, in a bad way.Checking the Execution Plan reveals that both queries have the samesteps, but, on the MSDE system the largest consumer in the process isthe Clustered Index Scan of the 630 record table (DB1 in my queryexample), using 85%. The next big consumer is a Clustered Index Seekagainst the other table (2,700 rows), using 15%.The Execution Plan against the Express system reveals basically theexact opposite: 27% going to the Clustered Index Scan of the 630record DB1, and 72% going to the Clustered Index Seek of the 2,700record DB2.I'm sorry to be stupid but I have this information but I don't knowwhat to do with it. The best that I can tell from this is that thisis the source of my problems. My problems are that on my currentsystems that my clients use the data is returned to them faster thanthey can click the mouse and that the new system (that is, when theychose (or are forced by attrition) to move to Vista and thus Express2005) the screen pop is like 1.5 seconds. This creates poor userexperience. Worse, one process I allow the users to do goes fromtaking 14-30 seconds to over 4 minutes (all on the same machine withthe same OS and version of my program, so it's not a machine or OS ormy app problem).Anyway, I hope someone can shed some light on this now that I've paredit down some.Thanks in advance.--HC
View 9 Replies View Related
Hi,
Our current environment is: SQL Server 2000 backend; XP/Windows 2000 clients with MSDE loaded; a Microsoft Access 2002 app using DSN to connect to the local MSDE database; Merge replication which is a job within the MSDE engine that we execute in VBA code using the following DMO code:
' Find the Job name to execute
lngJobCount = oServer.JobServer.Jobs.Count
lngJobIndex = 1
blFoundJob = False
While lngJobIndex <= lngJobCount And blFoundJob = False
strJobName = oServer.JobServer.Jobs.Item(lngJobIndex).Name
Me.lstJobs.AddItem strJobName, 0
If InStr(1, strJobName, "LEXData", vbTextCompare) > 0 Then
If InStr(1, strJobName, strServerName, vbTextCompare) Then
blFoundJob = True
End If
End If
lngJobIndex = lngJobIndex + 1
Wend
' Execute the job
If blFoundJib Then
Set oServer1 = New SQLDMO.SQLServer
With oServer1
.LoginSecure = True
.Connect strServerName
End With
Set oJob = oServer1.JobServer.Jobs(strJobName)
End If
We are now planning a move to a SQL Server 2005 backend and Express edition on the clients and the app would remain as Access 2002. Any pointers to documents that will be useful would be appreciated but I have a couple of specific questions as well.
1) As I understand it we can load Express side by side with MSDE so we will probably go down that path and load the data from MSDE into an Express version of the database. Once that's done we will create a DSN pointing to the new database and name it the same as the DSN which is currently used for the MSDE database. If we do this will our Access app simply work as before (ignoring replication)?
2) When we have our app happily running against a DSN that points to an Express database would we expect our existing DMO code (as above) to work, e.g. find a particular job in a list jobs and executes it? I can see that the replication job itself may have to be rejigged for Server 2005.
TIA - Peter
Hi,
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
I need to create the script to upgrade the current named instance of sql 2000 desktop engine to sql server 2005 express edition. I am having difficulty preparing the template.ini and would appreciate help.
[Options]
INSTANCENAME=MY_INSTANCE
SQLBROWSERACCOUNT=NT AUTHORITYNETWORK SERVICE
SECURITYMODE=SQL
SAPWD=music
UPGRADE=SQL_Engine
SQLBROWSERAUTOSTART=1
RSCANINSTALLDEFAULT=0
RSCONFIGURATION=FilesOnly
RSSQLLOCAL=0
I get an error that this file is invalid..Any clues? I am trying to upgrade existing instance of msde 2k to sql express 2005 and uses sql authentication
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