I'm doing a migration of CRM systems.

It's $500 for them to give me a copy of my database. Migrating it over to SQL Server .BAK file. It's a 75 GB file.

I need the data in x2 places. It's $500 per copy. If I pay for x1 copy. Is there a way for me to make a copy of the data. So I can have it on x2 USB drives. Drive one goes to CRM for sales team. Drive #2 goes to the new Applicant tracking system for the recruiting team.

I'll say I know virtually nothing about SQL from a dev or admin perspective. Just wondering if there is a easy way for me to duplicate & authenticate the data.

I don't see why not? We copy SQL Server backups all the time. $500 per copy seems really steep for db that is that small. Once you get the first copy simply cut and paste to where you need to second one.

Yep, no problem. .Bak file is just that...a file. You can copy it anywhere you want. What I'm not quite clear about is what you plan to do with it afterwards...are you restoring the same data into two different production systems?

quote:

Originally posted by Bytes:
I don't see why not? We copy SQL Server backups all the time. $500 per copy seems really steep for db that is that small. Once you get the first copy simply cut and paste to where you need to second one.

I am guessing that should be copy and paste.

quote:

Originally posted by 92fstech:
Yep, no problem. .Bak file is just that...a file. You can copy it anywhere you want. What I'm not quite clear about is what you plan to do with it afterwards...are you restoring the same data into two different production systems?

Exactly. I have one system now with Client Data & Candidate data.

The new system I'm going to will have client data on a CRM for the sales team. Then candidate data on a separate ATS (Applicant Tracking System). So I the data will need to be mapped differently to x2 separate systems. I want to be able to express mail the database to the new vendors for speed. That way I don't have to pass one USB stick around.

quote:

$500 per copy seems really steep for db that is that small.

Exactly. That's why I wanted to make sure I could just rip a copy over to my hard drive. Then paste on a new USB drive.

That's exactly how I've always moved a SQL Database from one SQL Server to another - back-up, copy/paste, restore.
You'll probably also have to copy SQL Ids and do some security setup as needed.

quote:

I want to be able to express mail the database to the new vendors for speed. That way I don't have to pass one USB stick around.

Dropbox or the like, and send them an email link to the data?

quote:

Originally posted by WaterburyBob:
That's exactly how I've always moved a SQL Database from one SQL Server to another - back-up, copy/paste, restore.
You'll probably also have to copy SQL Ids and do some security setup as needed.

I'll basically just have access to the single .BAK file. The new software guys that receive the .BAK will have to do everything else. I just want to make sure I can get the data to x2 places at the same time. Without the extra $500 extortion charge.

quote:

Originally posted by myrottiety:

quote:

Originally posted by 92fstech:
Yep, no problem. .Bak file is just that...a file. You can copy it anywhere you want. What I'm not quite clear about is what you plan to do with it afterwards...are you restoring the same data into two different production systems?

Exactly. I have one system now with Client Data & Candidate data.

The new system I'm going to will have client data on a CRM for the sales team. Then candidate data on a separate ATS (Applicant Tracking System). So I the data will need to be mapped differently to x2 separate systems. I want to be able to express mail the database to the new vendors for speed. That way I don't have to pass one USB stick around.

I guess my big question is how are you going to keep your data current and synchronized when you have a separate copy in two separate systems? I've always been a fan of keeping data in one place and accessing that single data set from multiple systems, rather than the other way around.