I created a snapshot replication and after the first replication process i didn't find the triggers and constraints on the subscription side. what happened ? did i do anything in bad or i can't replicate this objects? This necessary for me because i need to create a testdatabase about the production environment - periodically.
When updating data using .NET 2.0 SqlDataAdapter and a strong typed dataset, it seems that constraints (foreign key) and trigger are disabled. I'm using a stored procedure to delete rows and calling it from SSMS causes the trigger to fire. Calling it via the SqlDataAdapter not.
Can someone confirm this?
At least here, my triggers don't fire.
How can I enable, that triggers in SQL Server do fire?
Are there differences in this behaviour when using batch updates or not?
in merge replication using sql server 2005 and sql server compact, is it possible to have triggers (or business logic) for any changes on the client side? how does a client app know an insert/update/delete has been made? also, if the article is set to download-only, can the client app also be nofied of any changes?
i have setup default transactional replication using locat distributor scheme. I need to create triggers on tables at subscriber side. Can this be done using transaction replication?
How does one know what a particular trigger or constraint is supposed to be doing on a table. I am just two days old on this position, and no form of documentation, at the same time I am expected to trouble-shoot some error messages. Thanks for your help.
I have several sql server databases that were recently moved to a newserver. In the process of migrating the databases, any triggers andconstraints attached to tables were removed on accident. I need to addthese objects back into the databases, however I'm worried that I willhave problems with referential integrity since there is a chancesomeone may have deleted or updated a record that should have cascadedchanges to other tables but did not since the triggers and constraintswere missing. Is there an easy way to check for problems of thisnature in the databases?Also - I am planning on generating a script from the database on theold server that scripts the triggers and constraints, and then useQuery Analyser to run this script against the database on the newserver. Is this the best way to add these objects back into databasesthat are already populated with data and running on a live server?In in a pretty bad position, but at least these are databases that arenot accessed too frequently, so I'm hoping any referential integrityproblems will be minor.Any help or advice would be greatly appreciated.
I have a question concerning setting up data integrity checks in SQL Server.
I have a table that lists "Groups" to which an Entity belongs. The Entity can belong to multiple Groups. Every entity has 1 and only 1 of its Groups designated as the "Primary Group". Based on this, my table contains multiple records for each Entity. Each record describes 1 Group of which the Entity is a member. In this record, there is a bit field indicating whether the Group is the "Primary Group".
In other DBMS's I have implemented a check constraint on the "Primary Group" column to enforce the business rule that "a Entity may have one and only one Primary Group". I am aware now, that in SQL Server 7, I must implement this rule as a trigger, or in the client or data services layers.
Does anyone know if SQL Server 2000 will allow me to write such a check constraint?
I have been given the task of moving certain tables (that have PK, FK Constraints) from an existing Database (A) to form another Database (B) but making sure all the references to other tables in the original DB (A) are not affected. I was talled that triggers can solve this but I am not sure where to start. The Question is what I am looking for to replace, and how ??
Hi, I´m facing teh following situation:This are just sample table names, but should do for discussingpurpouses.Create table Invoice(InvoiceID Integer Not Null,CustomerType Integer Not Null,CustomerCode Integer Not Null,Amount DECIMAL(10,2) Not Null,.................)Create Table Type1Customer(CustomerCode Integer Not Null,...............................)Create Table Type2Customer(CustomerCode Integer Not Null,...............................)I need to add a way to restrict the CustomerType and CustomerCode,in the Invoice table to the correct values.This means that if customerType equals 1 the customerCode should bechecked against Type1Customer and if customerType equals 2 thecustomerCode should be checked against Type2Customer.I succesfully created a check constraint. That ensures that the validvalues exists when the rows in the Invoice table are inserted orupdated, but doesn´t prevent from deleting records from tablesType1Customer and Type2Customer that are referenced from the Invoicetable.Are triggers the only way to go?Thanks in advanceSebastián streiger
I have to migrate all objects alogwith all constraints,SP,Triggers, indexes etc from Development instance to Production instance of a DB, all those things are created through wizard ie. Sql server 2000 Enterprise Manager. if i use DTS it only mirates data along with tables and views but constraints,SP,Triggers, indexes etc not yet copied.
can any body help me how can I solve this problem by copying all objects alogwith all constraints,SP,Triggers etc from Development instance to Production instance.
I have a Windows 2003 Server running IIS 6.0 and SQL Server 2005. I have just (Today) deployed the first ASP.NET application (developed in Visual Studio 2003 and, as such, dependent on .NET Framework 1.1) on this server and am getting HTTP Error 403 (You are not authorized to view this page). This ASP.NET application runs fine on another server that is configured with the OS=Windows Server 2003, IIS=6.0 but without SQL Server 2005 and without the .NET Framework version 2.0. I found in the IIS Application configuration (on the troublesome site) that my app (in the Default Web Site folder) was pointing to the version 2.0 aspnet_isapi.dll. All efforts to use aspnet_regiis to "re-align" my app with version 1.1 have been fruitless to eliminate the HTTP Error 403. I granted the NETWORK SERVICE account privledges to the wwwroot folder. At this point, I don't know if I have a Framework error or a privileges problem.
I am trying to migrate from my current system, where I do merge replication from Windows Mobile devices running SQL Server CE 2.0 to a central database running SQL Server 2000 sp3a. I want eventually to move to a system running SQL Server 2005 CE replicating to a SQL Server 2005 back-end. But the transition will need to be gradual, and I may have to support both systems for a while until I can convert all clients from the old system to the new. I also need to do thorough testing.
So ... I'm trying to set up a test environment giving me the maximum possible flexibility to do my testing. Ideally, I'd like to set up SQL Server 2000 and SQL Server 2005 on a side-by-side basis, in a manner that would potentially allow mobile devices running both SQL Server CE 2.0 and SQL Server 2005 CE to sync with either back-end server.
Can someone provide me with guidance as what is possible to set up here? I know that SQL Server 2000 and 2005 can be installed side-by-side on the same server. It also appears that you can set up SQL Server 2000 so that EITHER SQL Server CE 2.0 OR SQL Server 2005 CE can sync with SQL Server 2000 (see www.microsoft.com/sql/editions/sqlmobile/connectivity-tools.mspx), but I don't know if it's possible for BOTH SQL Server CE 2.0 AND SQL Server 2005 CE to sync to the same SQL Server 2000. As for SQL Server 2005 ... it appears to be possible to set up SQL Server 2005 so that BOTH SQL Server CE 2.0 devices AND SQL Server 2005 CE devices can sync to the same SQL Server 2005 (see web page cited above). However, I don't know if it's possible to set up a SQL Server 2005 server installation in this manner while at the same time having a side-by-side SQL Server 2000 installation supporting any level of mobile merge replication.
I will soon be embarking on an upgrade of a transaction replicated database (Push) from 2005 to 2012 SP2.The publisher, distributor and subscriber are 3 separate machines.There databases will be detached, MDF and LDF will be copied across. Once attached, replication will be set up from scratch.
The name of the new servers are NOT the same as the existing ones.Should I completely remove transaction replication user the wizard and unticking the DB from being a database for transactional replication or just stop the log reader agent?How can I make sure the last of the transactions have gone across before I detach?Should I detach the subscriber first or the publication? Does it even matter?
Is there a better way of moving across the databases? I for one would have preferred to backup (.bak) then restore on the other side. I'd love to hear opinions on this as well.
I am working to create a phone list that will contain Last Name, First Name, and Phone Number sorted by last name. For printing purposes I would like to have three columns of data instead of the standard of one column.
Is it possible to create a query to present data in three columns showing the data side by side?
I have downloaded and installed VS C# Express Orcas beta 1. It appears that Express editons ov VS can only connect to SQL2005 Express and not to a high end edition which I have on my computer. In one of the Orcas forums, it was suggested that I can install SQL2005 Express side by side my high end SQL 2005. To play it safe, I wanted to get a confirmation from this forum before I do that. Is a side-by-side installation ok? thanks.
would like to know if it's possible to install SQL Server Failover cluster instance with shared storage along with standalone installation with Always on ( always on uses WSFC underneath).
Here is my case: I've a server running Windows server 2003 edition and SQL2000. I've installed SQL2005 using the side-by-side method as described by MSFT docs. I've then copied the mdf & ldf files to new locations and attached the db in SQL 2005 management studio. Every thing fine. Next, I've migrated the DTSs using the DTS migration wizard. After this step I have some bad warnings in windows:
When I restart the server I get the following message: "mmc.exe Microsoft Management Console encountered a problem and needed to close". Furthermore: I can't start the old SQL enterprise manager. It shows another error "mmc.exe - Entry point Not Found" and closes it self.
The MSFT support page on this error relates it to Windows XP but my system is running Windows server....
Any one has any idea why this is happening? Any suggested course of action?
My system is already installed with SQL server 2000 . Is it possible for me to install SQL server 2005 BETA CTP in the same machine and run both side by side.
I was trying to do something like puting two tables side-by-side inside a list, and list itself is grouped by a field. But for some reason, two tables are not organzied pararally even there is no page break inserted.
I need to migrate from sql 2000 to 2005 and in place upgrade is not possible. I can move the databases, logins but can some one help me to migrate sqlmaint plans and dts packages to 2005.
We have some developers who manage SQL2000 servers from their WinXP workstations using Enterprise Manager. We have now rolled out our first SQL Server 2005.
Can we install the SQL2005 Management Studio side-by-side with Enterprise Manager on these WinXP workstations?
If not, what are most people doing in these cases?