.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links


Posted By:      Posted Date: October 28, 2010    Points: 0   Category :Sql Server
Hi. I just upgraded my server from SQL Server 2005 Standard edition to SQL Server 2005 Enterprise edition (http://benchmarkitconsulting.com/colin-stasiuk/2009/06/03/sql-server-2005-edition-upgrade/). Then applied the service pack again. After the computer restart, when i opened the replication monitor to check then effect this upgrade had on my replications, i got below error when i open the Subscription Detail window. any suggeestions/workaround to correct this shall be very much appericiated. Thanks

TITLE: Replication Monitor

Replication Monitor could not open the Detail Window.


Specified cast is not valid. (ReplicationMonitor)



View Complete Post

More Related Resource Links

MS SQL Server 2005 Standard or Enterprise with default encryption

Hi, I wish to know whether or not by default MS SQL Server 2005 Std or Ent edition will encrypt the communication over the network by default? As, when we test out the database activity monitoring solution to capture the SQL traffics from the network, we are unable to see the DB user name and Source Program but SQL statements is able to seen. According to the vendor, it is due to the nature of MS SQL Server 2005 that encrypt the communication by default. But, why is it only encrypted the DB user name and Source Program but not the SQL statement? Can someone provide me the answer? Is that true what the vendor claims?   regards, Teh

SQL Server 2005 standard Edition to SQL Server 2005 enterprise edition



My current version of SQL server is Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)   Nov 24 2008 13:01:59   Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

I want to upgrade this to Enterprise edition. I would like to know the below information please

  • step by step instructions on how to perform this upgrade
  • I have databases & replications setup on this server. Will the upgrade have any adverse effects on the current replication setup?

Any help and guidance is truly appericiated. Thanks.

Slow sql-server after upgrade from SQL-Server 2005 x64 standard to SQL-Server 2008 R2 x64 enterprise


We moved our databases to new hardware today (using copy database wizard)


The new hardware should be better than the old one.

We went from 28 GB ram to 128 GB.

We went from 16 cores to 32 cores (with even more cache etc.). We also moved from external SAN with 40 disks to intern disks (8 Samsung SS805 100gb ssd slc)

                             According to our own metrics we could get twice the IO using IO m

sql server 2005 enterprise edition is required


sql serve 2005 enterprise edition is required to work with microsoft enterprise blocks


SQL Server 2005 Merge Replication

We did the following: We setup a database with all of standard tables, views, etc. We then put in place merge replication for a few of the tables within this database, including a tables called "Areas". We can execute SQL statements to insert rows into this table fine. We then applied an update script for this database to change a few tables by adding fields and changing indexes, etc.  We didn't change the "Areas" table though. After the update to the database structure, we get an error when trying to insert into this "Areas" table. The error message was the following: The insert failed. It conflicted with an identity range check constraint in database 'AETest', replicated table 'dbo.Areas', column 'AREPrimaryId'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.  The statement has been terminated.   What would cause such a problem and how do we resolve it?  The structure of the "Areas" table before and after the update is the following: USE   [AETest] GO /****** Object: Table [dbo].[Areas] Script Date: 08/24/2010 17:42:36 ******/ SET   ANSI_NULLS ON GO SET   QUOTED_IDENTIFIER ON GO SET   ANSI_PADDING ON

Can't connect to SQL 2005 Enterprise using Management Studio with Server Name (only (local) works

This is a test system, everything running locally & no domains. Win 2003 Ent. Server & SQL Server 2005 Enterprise. I can't log into SQL Server Management Studio using the server name & using either Windows Authentication or SQL login. If I change the name of the server in the drop-down list to "(local)", I connect just fine (both Windows & SQL security modes). Shared Memory, Named Pipes & TCP/IP enabled in both server & client. Remote connections allowed. I have IP adresses (both & external IP) in my hosts file pointing to the server name. Does SQL require a DNS server? This wouldn't be a problem except for the fact that I can't install SQL 2005 SP3 due to authentication failure since there's no way to enter (local) as the server name. SQL tools (management studio, SP install) seem to see the SQL server running but won't authenticate the user through any means other than setting server name to (local). This is driving me crazy!!!

Does SQL 2005 Enterprise Edition come preloaded on Windows Server 2003 Virtual Server.

Does SQL 2005 Enterprise Edition come preloaded on  Windows Server 2003 Virtual Server. I found this link http://www.microsoft.com/downloads/details.aspx?FamilyID=77f24c9d-b4b8-4f73-99e3-c66f80e415b6&displaylang=enMr Shaw

Replication between SQL Server 2005 and SQL Server 2008

Hi,    We were using SQL Server Transactional Replication between two SQL Server 2005 servers. Now we are going to upgrade the Publisher server to SQL Server 2008, Distributor Server remains as SQL Server 2005.     Can anyone let me know what is the challenges we need to face when configuring Replication between SQL Server 2005 and SQL Server 2008. Replication Method - Transactional Replication Distributor/Subscriber - SQL Server 2005 Publisher     -  SQL Server 208 Regards, Fazlu.

ODBC connection to SQL Server 2005 Standard (on windows xp) with Windows authentication does NOT wor

I reviewed lots of postings, still could not find an answer. If I choose Windows authentication: - with TCP/IP and "Dynamically determine port" checked, I get the following error "The user is not associated with a trusted SQL Server connection; - with Named Pipes, Server Name & Pipe Name as "VSAXAONG", I get two errors, one after the other on the same pop-up:       Connection failed  SQL State 01000  SQL Server Error 1385 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] ConnectionOpen (Connect()).       Connection failed  SQL State 08001 SQL Server Error 17 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] SQL Server does not exist or access denied. If I choose SQL Server authentication and fill in the password - the ODBC connection works fine. I have to say that I created two different logins on the server, one for Windows authentication, and one for SQL Server authentication - both for the same Windows user name. I would appreciate any help I can get on this.  Thank you all in advance.

Using SQL Server Replication for SQL Server 2005 and 2008

I have an ASP.NET application that uses replication, and uses the RMO DLLs to do this. I initially built the application against the 2005 version of the DLLs and have it running successfully against SQL Server 2005. However, when I try running it against SQL Server 2008 it doesn't work. Initially I didn't deploy the Microsoft.SqlServer.* DLLs with my app - instead relying on them being in place on the server on which it was installed. However, when trying to make it work against SQL Server 2008 it was looking for the 2005 version DLLs which it wasn't able to locate. Following some other advice I read online I have now swapped out the 2005 DLLs and referenced the 2008 assemblies in my .NET project. In my MSI I now also deploy (i.e. redistribute) the SQL Server 2008 DLLs to the bin folder of my ASP.NET project. Now, when I try to run the application against SQL Server 2005 it fails to load the Microsoft.SqlServer.Replication assembly. I run depends.exe against this and find that it's dependent on SQLNCLI10.DLL which is missing on my machine with only SQL Server 2005 on it. So, what am I to do? Is this possible? How do I get around this?

Why doesn't SQL Server 2005 Enterprise always shrink a log file after a backup?

I have several databases that, despite being backed up regularly, do not release space to the operating system.  In one extreme case, I have a log file that is less than 1% utilized (and has been for months.) I know how to manually force a shrink, but I should not need to do that on any sort of regular basis.  In fact, it is against best practices to manually shrink a log file (or any database file for that matter) because of the very high risk of an unrecoverable error. It is my understanding that SQL Server will eventually handle these things on its own.  However, it does not appear to be doing so.  Any thoughts as to why? Thanks, Dave

Problem Installing SQL 2005 Enterprise on Server 2008R2 Enterprise???

I am trying to install SQL Server 2005 Enterprise onto a new WinServer Enterprise 2008R2 box.  I am using my MSDN disk that contains the various flavors of SQL Server 2005.  When I select to install Enterprise (64 bit) version all that is available for installation are the client tools, no server tools.  When I install the Standard version, the server tools are available. Is there a problem installing SQL 2005 Enterprise on WinServer Enterprise 2008R2???

SQL Server 2005 Replication Alerts

Dear Friends,We had some problems related to SQL Server 2005 Transactional replication. The distribution agent wasn't working properly. I am relatively new to Replication, so please bear with me. I need to configure alerts. I decided upon the below 3 options (if any other option is there please let me know), Replication agent failure Replication Warning: Transactional replication latency (threshold expires) Replication Warning: Subscription expiration (threshold expires)To test the 1st option, I deleted a row in subscriber and updated that row in publisher. Since the row no longer exist the distribution agent failed. I even dropped the table in subscriber and tested. We received alerts. Now for the 2nd option the lateny was 30sec. So if a transaction happened in publisher it needs to be replicated to subscriber within 30 sec. If not Replication warning alert will be fired. I assumed that since the replication agent was failing in 1st option after deleting and updating the same row in subscriber, I thought that it will cause the transaction to be retained in the distributor for a long time and hence it will make the threshold to expire (2nd option) and hence the alert would fire. But it never happened. So my question is as follows:1. How to make an alert happen for option 2 and option 3 ?2. Was my assumption/intepretation correct wrt to option 1 forcing option 2 fire.- Deepak

SQL Server 2005 Standard edition install fails; An instance with the same name.../


Good Morning

I am trying to install SQL Server 2005 onto Windows Server 2003 Small Business Edition. Previously SQL Server 2000 from the SBE disk was installed, automatic updates are enabled.

I have selected the default instance and everything I try results in the error:

An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

Log file says;

Machine         : ISAINTERNET
Product         : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_ISAINTERNET_SQL.log
Last Action     : DetectInstanceClash
Error String    : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Error Number    : 28086

Ian Smith

Identity Range Value (Max Limit Finished) SQL Server 2005 (Merge Replication Problme)


Hi ,

I am using SQL Server 2005 enterprise edition, I Confirured the Merge Replication to my database). I have a replication of 21 database from various locations.

Problem is: When is trying to remove one subriction from the publisher and add a fresh subriciton to it. it is poping any error saying the Identity Range value exceed its Max Limit try to change from int to bigint. is there any solution for it not changing from int to bigint.

Thank you.


SQL Server 2005 bidirectional replication problems


I am having a system with two servers running SQL Server 2005 on Windows Server 2003.
Between the two SQL Server instances I am having a bidirectional replication of all my tables to always have the databases in sync.

When the replication is set up on the servers it normally runs fine for some time and then it stops working and I get errors like the following:

  Command attempted:
  if @@trancount > 0 rollback tran
  (Transaction sequence number: 0x000001B200005784000D00000000, Command ID: 1)
  Error messages:
  Violation of PRIMARY KEY constraint 'PK_MyTable'. Cannot insert duplicate key in object 'dbo.MyTable'. (Source: MSSQLServer, Error number: 2627)
  Get help: http://help/2627
  Violation of PRIMARY KEY constraint 'PK_MyTable'. Cannot insert duplicate key in object 'dbo.MyTable'. (Source: MSSQLServer, Error number: 2627)
  Get help: http://help/2627

And another error:

  Error messages:
  Agent 'SERV-A2-SYST-SERV-A1-10' is retrying after an error. 77 retries attempted. See agent job history in the Jobs folder for more details.

I do not know much about how the bidirectional replication works as I just set the replication up by some script

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend