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...
Can Express edition be a publisher for transactional replication with SQL-DMO? Does scripting out and editing it work? Does stored procedure work for this purpose?
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 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.
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.
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
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.
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.
I am using SQL 2012 SE and implementing transactional replication. I need to insert the rows from publisher database tables to new tables, drop the old tables and rename the new tables with the old table names.
For example:
Publisher database tables that are being replicated:
Table1 Table2 Table3
and I am going to create new tables in publisher database
Drop constraints from and then tables (does this require articles to be removed from replication?)
Table1 Table2 Table3
Rename
Table1_new to Table1 Table2_new to Table2 Table3_new to Table3
Does this require replication to set up from scratch or add the three articles only to replication? Is there a way this can be done without pausing or reinitializing replication or without removing articles and adding them back?
I have taken over a transactional replication setup that is being usedfor fault tolerance (I know, I know...).The scenario I am concerned with is where the publisher goes down due tofailure, so we need to point our application at the subscriber and startupdating the data there. We are not using the immediate updating option.How do I go about re-syncing the publisher with the data that been addedto, or changed on the subscriber, when the publisher comes back online?Thanks,TGru*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
I have configured transactional publication where some tables have a simple row filter. And I made a supscription to this publication. When I make snapshot and replication initialization, all rows are updated correctly and passed to subscriber. But when I change some column at a row included by filter at publisher, it is never updated on the subscriber. Other tables and that same table when I remove filter is updated correctly.
What can be problem?
I am using SQL Server 2005 Standard for publisher, and SQL Express 2005 for subscriber, both with SP2.
I have a primary and secondary servers both running Windows 2000 SP3 with SQL 2000 SP3. I have set up transactional replication with the primary server as publisher and the secondary server has the distributor and subscriber DB. I am testing the scenerio where my primary server goes down and I have to make updates to the secondary server until my primary server comes back up. I am able to update my subscriber database and the transactions go into the MSreplication_queue table to be pushed back to the primary when it comes back up. When I bring the primary server back up and start the queue agent job it starts pushing the transactions over and then stops after 4 or 5 transactions with the error "Failed while applying queued message to publisher". I have attached part of the log file for the agent below
In the sql server logs I am getting this message: Replication-Replication Transaction Queue Reader Subsystem: agent Repl Queue Reader failed. Failed while applying queued message to publisher. Error: 14151, Severity: 18, State: 1
Hi,I am trying to set up a Updatable Subscriptions for TransactionalReplication with SQL 2005 (queued updating).I have a stored procedure "SYS_spShellTest" which is replicated to thesubscriber viathe replication option "Execution of the stored procedure":-------------------------------------------------------------ALTER procedure [dbo].[SYS_spShellTest] @cmd varchar(1000)WITH EXECUTE AS ownerasBEGINEXEC @result = master..xp_cmdshell @cmd, NO_OUTPUTReturn (@result)END-------------------------------------------------------------1) If I call "exec SYS_spShellTest" on the publisher the call is alsoexecuted on the subscriber.2) If I call "exec SYS_spShellTest" on the subscriber the call is NOTexecuted on the publisher.How can I make 2) work so that it is also executed on the publisherplease?Thanks a lot,Patrick
Are there any requirements that dictate the SQL Server version for the distribution agent for a SQL 2000 publisher with a transactional push subscription to a SQL 2005 subscriber?
I want to have transactional replication setup with SQL 2000 as a publisher and SQL Express 2005 as a subscriber? Where can I get some documentation around that?
Basically, the problem I am stuck with is that while registering the subscriber in SQL2000, SQL2000 cannot recognize my SQL Express 2005 instance as a subscriber. I have tried both SQL Ent. Mgr. and sp_addsubscription.
Hi, I am looking to using the express edition toolkit for its BI tools but noticed the that it doesn't support a Database engine. If I am running SQL Express edition, & install the Express toolkit, will this remove the Database engine functionality of the Express edition? Will there be conflicts? Will they run as separate GUI's or is the toolkit added to the Express edition GUI?
Thank you very much for any suggestions anybody might have on this
I've installed Visual Basic 2005 express edition & tried to connect to SQL Server 2005 express edition. I noticed that VB2005 Express Edition doesn't have any OLEDB provider for SQL Server. The only OLEDB Provider is for M.Access. Is this correct? if so, what should i do if i want to connect SQL Server 2005 express edition with VB2005 express edition by using OLEDB connection type?
I really appreciate any respond from you guys.. Thank's and waiting for the good news..
Hello!M a newbie.. I just want to know, that wots the difference b/w SQL Server Standard Edition and Express Edition.?And can I use Visual Studio 2005 (Professional Edition) with SQL Server Express Edition.?
Hi i have two version of SQL server express (with Visual Studio 2005) and developer edition i am trying to access an sql database file -created by the express edition integrated with Visual studio- using a developer edition instance can i just attach it and access it. and can i use BI and reporting services on that file
I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?
I know people have put up this question before but I wanted some updated feedback. I just bought Visual Studio Tools for MS Office and it comes with SQL Developer Edition. I am currently using VS.net 2003 and using MSDE with MS SQL Web Data Administrator to build my dbs then export the sql script. I was wondering if I should uninstall the MSDE and install the DEv Ed so I can develop all the triggers, constraints etc through Enterprise Manager, therefore having a better setup DB. I know you can do all that through code but why reinvent the wheel. One last question, with the Dev Ed you just export the schema and scripts to a machine with SQL Server installed once the DB is ready for deployment ? Is this correct? I lied one more question, does the uninstall of MSDE leave much of a mess, what is the best way to get rid of it. Thanks in advance Pete
I am migrating from MSDE to Sql Server Comapct Edition.I want to how will it affect the code and how large the changes will be. For example will i need to change only the connection string or if some of the methods used by MSDE or not available in the CE version. Any information and ideas reagrding this will be useful.
In the past I've used MSDE with Visual Studio.NET 2003. I'm going to start studying for an MCP in SQL Server 2000 so I'll probably get SQL Server 2000 Developer Edition. Will I be able to install this on my PC if it already has MSDE installed, or will I need to remove MSDE, etc? If there are any other things I need to be aware of please let me know. Also should I stick with SQL Server 2000 while studying for the exam, or would I probably be able to use SQL Server 2005 with a book that uses SQL Server 2000? I don't know how different they are.
I recently upgraded my MSDE server to SQL Server 2000 database. After the upgrade, I see, every minute,in the logfile that the database is starting whilst in Enterprise manager the database is up and running. I would be grateful if you could bail me out of this anomaly.
hii download free starter kit timetraker application( i downloaded both Visual web devaloper and sql server express from the Internet) when i tried to run it it is showing the following errorAn error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)plz give me the solution above error thanks in advance vittal
I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005. Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.
MESSAGE:
1. First comes a window with the title: €œsetup.exe €“ Unable to Locate Component€? And it displays a message: This application has failed to start because MSTDCPRX.dll was not found. Re-installing the application may fix this problem. 2. After I click the OK button of this window it comes another window with the title: €œMicrosoft SQL Server 2005 Server Setup€? And it displays a message: Failed to load SqlSpars.dll
Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?????
Thanks for your help and support when you have time to respond. Sincerely, TonyC
MORE INFORMATION ON THE: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFiles
1. C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_B3-XP_Core.txt Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 87 Aborting queue processing as nested installer has completed Message pump returning: 87
2. C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Unable to load setup helper module : 87 Message displayed to user Failed to load SqlSpars.dll Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : 2 Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17 Message pump returning: 87
It's arriving from ebuyer tomorrow for 32 quid. I already have aninstance of MSDE running on the laptop and ideally i would like SQLserver to be installed and use the current instance and not installany other additional services. [hope i got my terminology correcthere.] Basically all i would like is to use the Enterprise Managerwith my existing MSDE database. I was wondering if there is anything ishould be doing before I install. Should i shut down the service orleave it running for instance.Thanks for any tips,AndyB
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
