All,
I have seven SQL servers with 1 or 2 databases on each. I need to move the databases and consolidate them down to one or two servers. I am new to this and hear about detaching and attaching the databases. Is this the way to go? If so, can someone tell me how. I am sure it's not as simple as copying the way things are done in the Windows environment.
Thanks
Hi All
I need some advice and I think I have a possible solution, I just need some approval that it is the right thing to do!
I have 73 Databases which I look after and they are all SQL 2000 and SQL 2005 DBs and backuing up these DBs is becoming an Administration nightmare. So what I was planning is to recreate all the backup jobs jobs on a SQL 2005 Server and monitor them from there!
Is this a good idea or should I think of something else?
Thanks In Advance!
Gopher
Can anyone point me in the direction of some best practice resources for consolidating Sql 2005 on a 64 but Unisys platform?
The web seems a bit sparse unfortunately and most of the best practice information seems oriented around 2000. This is a great article but Im not sure how much has changed in 2005 http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/64bitconsolidation.mspx .
here is the idea,
we are trying to automate our weekly import process. we are running the sub packages with it own configuration file in sequence. i want to integrate the process in to a main package ?
i also want to create a job to run this main package.
do i need any configuration file for the main package?
i know how to do it in sql2000 but i don't know in sql2005. can anyone point me in the right direction that would be great
thank you so much !
Hi
I have
Package1 and Configfile1
Package2 and Configfile2
and so on...
Currently i am running it manually one by one on SMS using integration services.
I have assigned to automate the process or consolidate into a single package.
I can automate it using execute package tasks without config file. there is no option
in the execute package task to point to the right config file.
Any pointers on this would be appreciated.
Hi guys, can you please tell me what are steps we need to take in order to consolidate two datamarts into one? My issue us that we have two datamarts and the client wants the data in these two marts to be in one mart. Please help. I will be grateful if you refer me to any documentation if possible.
View 1 Replies View RelatedCan anyone point me in the direction of some best practice resources for consolidating Sql 2005 on a 64 but Unisys platform?
The web seems a bit sparse unfortunately and most of the best practice information seems oriented around 2000. This is a great article but Im not sure how much has changed in 2005 http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/64bitconsolidation.mspx .
Hi all,
I am new to replication and have a few questions.
1) Are there any "hooks" available to insert processing when a subscriber is about to copy data from a replicating site?
2) Is it possible for a subscriber to change only his local copy of the data - without replicating the changes back to the publisher?
I realise that once the data changes in one place it isn't really replicated anymore, and I realise that my limited knowledge of the subject might well mean I'm not even asking the right questions. Therefore, I shall try to describe as best I can my scenario.
I wish to use many servers for transactional input (to distribute the workload) and use replication to publish the inputted data to a subscribing central site. One of the tables I wish to replicate has an identity column as primary key, but the records should otherwise be unique - i.e. no two records should differ only in the value of the key. Another table, which should also be replicated, uses this id value as a foreign key.
I can use the identity increment and seed to guarantee no key violations will occur when copying data to the central server. However, there is another issue: Several servers can create the same record but with different id values.
I need to "merge" such records by deleting duplicate entries in the table with the identifier as primary key, and update the foreign keys correspondingly. To clarify (I hope!), here's an example of what data I might have on the central site after copying data from two input sites:
TRANSACTION table
amount = 200, metadata_id = 1001 // Replicated from server INPUT_1
amount = -117, metadata_id = 2001 // Replicated from server INPUT_2
METADATA table:
id=1001 Actitiy=Sales, Country=USA
id=2001 Activity=Sales, Country=USA
What I would like is basically for the central site to identify that metadata 2001 is really the same as metadata 1001, update the foreign key in the TRANSACTION record accordingly and not import (or delete, if this "merging" is done in a post-treatment) the duplicate metadata record.
If anyone can offer any advice on how to achieve this I would appreciate your input.