Is It Possible To Replicate Between Two *Default Instances* ?
Oct 19, 2005
Hi all,
I have two SQL Server installation on two seperate machines that both ones were installed using *default instance*,I mean they are not *Named instances*.
My question is: Is it possible to replicate between two servers? Or both should be named instances? I heared that one of the reasons that *Named instances* are preferred is that replication and SQLMail is not feasible on default not named instances.Is this true?
-Thanks
I had a server with SQL Server 7.0 I installed a named instance of SQL Server 2000 and then i passed all my DB of the 7.0 instance to the 2000 instance. Then i removed the 7.0 instance, that was the default instance. So at the moment there is only the 2000 version, but it isn't the default instance Can the 2000 instance become the default instance? (So that clients can connect to it simply through computer name, and not creating an alias)
Hi, I am trying to replicate some of my production tables into development tables in an automated way. Decided to use the Select INTO command because it seemed to be the easiest way. This command does copy all the col sizes, but does not copy over the "default value or binding" fields. How do I do this? I saw that in create table you can use "INCLUDING COLUMN DEFAULTS "
But this doesn't seem to work for the select into command. Can you tell me how I can do this? Currently the command I am using is:
SELECT * INTO " + DevTableName + " From " + ProdTableName
However, this won't copy over the default column values that I have specified inside the table ProdTableName. Can you tell me how I can do this?
I have a server computer named 'X' and I would like to install 2 instances of SQL Server 2005
1. SQLTEST
2. SQLDEV
During installation. if I select Default instance then it will name my sql server instance X . I don't want that. I want to have essentially 2 named instances to make it clear to the users that they are using a test and dev sql server. Whats the best way to do this? I am open to suggestions if there is a different way to do this.
Is it required to have a default instance? Can I have 2 named instances XSQLDEV and XSQLTEST?
Also, on the SQLTEST I will be installing reporting services. By not having a default instance will it cause issues for the SSRS installation.
I am tasked with correcting 600 SQL Server instances default settings. I would like to use powershell, if possible to loop thorough each named instances (I have a list) and apply the following settings. I also need to query the server for the installed memory and apply * 80% logic for maxmem, and look at the VCPU count and adjust the MAXDOP to that number.
USE MASTER GO EXEC sp_configure 'recovery interval (min)', '0'; RECONFIGURE WITH OVERRIDE; EXEC sp_configure 'allow updates', '0'; RECONFIGURE WITH OVERRIDE; EXEC sp_configure 'user connections', '0';
Using SQL 7.0 I'd like to replicate just schema from DB on server A to DB on server B, then be able to replicate data only form DB on server B to DB on server A. I need help!!
Thanks for ANY information you can give me... ~Jepadria
When I am in Visual Studio 2005, and I try to add an SQL database, I get the following error "generating user instances in sql server is disabled. use sp_configure user instances enabled to generate user instances." I am currently using SQL server 2005 Express. What do I need to do, to create an SQL database? Thanks in advance.
I am new (very new) to SQL. I 'm trying to set up SQL 7 to replicate a particular table on a daily schedule and then FTP the file out to a remote directory. Sounds easy! I'm sure it is, I just need someone to walk me through the steps.
If anyone can help me out I would really appreciate it.
I'm replicating with SQL Server 2000(updated Service Pack 3) get error:
SQL Server Enterprise Manager could not configure 'BREEZE1' as the Distributor for 'BREEZE1'.
Error 14113: Could not execute "'"C:program filesmicrosoft sql server80 ools\binnosql" -E -l60 -t60 -d"distribution" -b -i"c:MSDESQLBinnMSSQL\installinstdist.sql" -o"c:msdesqlinnmssql\installinstdist.out"'". Check 'instdist.out' in the install directory. 'distribution' is not configured as a distribution database. Deleting database file 'c:msdesqldatamssqldatadistribution.ldf'. Deleting database file 'c:msdesqldatamssqldatadistribution.mdf'.
I have a feeling this is failing because I have not C:msdesqlinnmssqlinstall directory at all.
Is there something I'm doing wrong...If the SP3 can affect???
declare @filenumber as char set @filenumber = '65'
declare @filenu2 as char(6)
set @filenu2 = CONVERT(CHAR(6),(replicate('0',(6-len(@filenumber)))+ @filenumber ))
select @filenu2 as x
This should return 000065 but it returns 000006 i have stepped through it the replicate should replicate the 0 4 times (6 - len of @filenumber) instaed its doing it 5 ??
Merge replication. We switched a publication over from push to pull and are now initiating everything within an application. We have just encountered a situation where it is now completely impossible to replicate DDL.
When this was a push subscription, we could execute the following and it would fly straight through the engine and hit every subscriber without having to do anything at all:
ALTER TABLE <tablename>
ADD <columnname> <datatype> NULL
Now that it is a pull subscription when I issue an ALTER TABLE and add a nullable column to the end of the table, it does NOT replicate at ALL. We get the following error message:
The schema definition of the destination table 'dbo'.'Player' in the subscription database does not match the schema definition of the source table in the publication database. Reinitialize the subscription without a snapshot after ensuring that the schema definition of the destination table is the same as the source table. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199478) Get help: http://help/MSSQL_REPL-2147199478
The process was successfully stopped. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199481) Get help: http://help/MSSQL_REPL-2147199481
It apears that we are now required to either reinitialize every subscriber every time we add a column or we are required to first distribute the DDL change to each subscriber, make sure they all have it, then add it to the publisher before anyone replicates, and then reinit every single one of them without a snapshot. This makes absolutely no sense at all.
The interesting thing is that we can add articles at will and those get applied with absolutely no problems at all to the subscribers without having to do anything other than add the article and generate a new snapshot.
Hi everyone, I've recently been thrown into a DBA role (I've never done any DBA work except writing a few SQL queries), so please go easy on me if these are stupid questions. My first task is to find the best way to replicate data between two SQL Server production databases. The data is to come from Production DB #1 to Production DB #2 (for access by a different system). The data has to be super-close -- not necessarily real-time, but within a few minutes. So when data is updated in #1, #2 shouldn't be be lagged by more than 45 minutes (5-10 is ideal). There are hundreds of thousands of records.What would be the best way to do this? Are there options in SQL Server 2005 to do "differential" updates from DB1 to DB2? Or is that how "transactional replication" works? If we were to implement a "full recovery model", will this impact any sort of replication? Thanks.
WE have a production database that we need to sync with about 100 salesman's laptops. These laptops will not always be online and would need to sync on the fly.
We are thinking of having a separate distribution database to handle the load and creating either a pull subscription or even just a DTS package. We would like to have the salesmen just signon and go to an ASP page and hit an Icon and either the pull subscription or the dts package would start the sync..
Anyone tried this before and have any other ideas??
I have set up a simple trans rep from a server in the office to the web. both servers are NT4sp6aSQL 7.0. Tables only.
The publication and distribution db are on the server at the office, and there is a full time connection through the firewall.
The initialization and first replication works perfectly, but after that, there is a message from the snapshot agent that "no subscriptions needed initialization", the logreader says thare are no replicated transactions and the Distribution agent says there are no replicated transactions. What am I missing?
Hi, there I have a situation here.... I have Production DB and Development DB in the same SQL7.0 box.... I want to update the data and SP from Pro. to Dev at least once a day... So this is my plan.
1. Back up(Pro.) and restore(Dev.) so I can have the same DB in the same box. 2. Using a Replication (Pulication and Subscription) ro update the data and SP. 3. Because DTS can not update the SP, I use the replication instead of DTS. I need to update the SP, too..(Front end is ACCESS and backend is SQL7.0 DB)
Is there any other methods or way to make ti happen... Any suggestion can help...
I'm new to replication. I configured Server named TESTER as publisher & distributer. Create new publication for database named TEST ( type : Transactional ), then Create a new push subcriptions for database TESTREPLICATION ( on the same Server : TESTER). Then I open a table in database TEST to input some data but I couldn't see any tables or data in database TESTREPLICATION ( I chose Continuously, not scheduled).
Yet, after the lunch, I could see the tables, no data. I tried to choose Start Synchronizing but not helped.
Could someone please point me in the direction on where to look for info on how to: Replicate an MS SQL 6.5 tables on an Oracle 10.2.0 server every 5-10min?
Hi: In the publishing server, admin users could change and non-admin user password and also add login and drop login.
How could it happen to not only replicate the application database to subscriber server but also replicate the changes made in master database? So that the remote subscriber server will have the most current login updates?
When I'm using MS SQL transactional replication and select all the tables to be replicated, some of the tables are marked with the red cross signs and aren't being replicated. How do I include these tables into the MS SQL replication? I tried to build indexes and re-created publications, but it didn't work.
Hi all, I have done the replication its working good.Now i have created the new table in publisher. but i have created the same table in sub scription too. how can i replcate this new table..?
Hi !Hi !I'm thinking of installing a Microsoft SQL Server 2000 on a database server,to be the db of a webapplication, but the it must be possible for the usersto copy/replicate data from the server db, to a local db on their e.g.laptop to work even if not online. Is there a tool that can handle thisscenario. (it must be possible to update the server db from the laptop whenonline again ).And:What have to be installed on the laptop (apart from my application runningon the replicated data) ?Thanx/Hans
I have a db and I only really need the table structures and defined functions/procedures from the db. A small sample set would be nice from each table, but not necessary.
What would be the easiest way to accomplish this?
I'm getting the db from a server not connected to the new one so I either need to get the files and reattach or I need to just copy the structure/procedures in.
Trying to build an replication and subscription beteween db in SQL 2000. The db holds our business system (Dynamics NAV, earlier Navision) and several of the tables include $, spaces and even :
We can take some of this away when creating a new db or make scripts for some actions but I wonder if the mirroring in 2005 could handle this?
My environment are Win Vista, Ms sql 2005 express, Ms Sql Server Management studio express. I have a database Mysearchdb.mdf and want to replicate Myseachdb.mdf to another database with exact same features. What is the best way to do it? I don't want to create each tables, functions and store procedures manually. Thanks
I am relatively new to replication. I have a rather dumb question. I have two SQL Server databases, If i make a change in the first database schema, i want it to replicate to the second database. i dont want the data to replicate though. Is this possible?
