SQL Server Management Studio: databases

Showing posts with label databases. Show all posts

Friday, March 30, 2012

migrating from Access to SQL Server

Our organization has about 10 multiuser Access databases that I'm
considering migrating to SQL Server. Currently, these split databases
perform reasonably well in Access over our LANs, but slow over the T1 lines.
However, we occasionally run into corruption problems, and we would
eventually like to develop some browser-based applications to work with our
data.
Most of these databases have dozens of queries and form controls also based
on queries, so the most realistic strategy for us in the short term would
probably be to just migrate the data, and link the remaining Access front
ends to the tables in SQL Server.
However, I'm wondering if we will accomplish much by taking such a step,
since all the queries will still be in the front end. I understand there
would be a performance improvement if we had the resources (which we
currently don't) to convert those queries to views and stored procedures in
SQL Server. But if we only move the data tables to the back end, do we
really obtain enough of a benefit to justify taking even that step?
Thanks in advance,
Paul
Hi,
Please do not misunderstand moving data from Acess to SQL Server would
increase the performance, it is still based on the design of the databases
and all the indexes. I would recommend to move from Access to SQL Server
since SQL Server can support more concurrent users and it provides better
security and data import/export functions.
Ed
"Paul Ponzelli" wrote:

> Our organization has about 10 multiuser Access databases that I'm
> considering migrating to SQL Server. Currently, these split databases
> perform reasonably well in Access over our LANs, but slow over the T1 lines.
> However, we occasionally run into corruption problems, and we would
> eventually like to develop some browser-based applications to work with our
> data.
> Most of these databases have dozens of queries and form controls also based
> on queries, so the most realistic strategy for us in the short term would
> probably be to just migrate the data, and link the remaining Access front
> ends to the tables in SQL Server.
> However, I'm wondering if we will accomplish much by taking such a step,
> since all the queries will still be in the front end. I understand there
> would be a performance improvement if we had the resources (which we
> currently don't) to convert those queries to views and stored procedures in
> SQL Server. But if we only move the data tables to the back end, do we
> really obtain enough of a benefit to justify taking even that step?
> Thanks in advance,
> Paul
>
>
|||Good points. Thanks, Ed.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:1F01575D-FA7D-4C73-ADC6-F205B7B035DD@.microsoft.com...[vbcol=seagreen]
> Hi,
> Please do not misunderstand moving data from Acess to SQL Server would
> increase the performance, it is still based on the design of the databases
> and all the indexes. I would recommend to move from Access to SQL Server
> since SQL Server can support more concurrent users and it provides better
> security and data import/export functions.
> Ed
> "Paul Ponzelli" wrote:
|||"Paul Ponzelli" <begone@.spam.forever> wrote in message
news:enIRb3vPFHA.3596@.TK2MSFTNGP15.phx.gbl...
> Our organization has about 10 multiuser Access databases that I'm
> considering migrating to SQL Server. Currently, these split databases
> perform reasonably well in Access over our LANs, but slow over the T1
lines.
> However, we occasionally run into corruption problems, and we would
> eventually like to develop some browser-based applications to work with
our
> data.
In addition to the valid points that Ed made, SQL Server is far more
resilient to data corruption than Access.
Steve
|||Another reason to make the move.
Thanks, Steve.

Migrating ext drive array

Please consider the following scenario
I have sql 7 NT server the application is on the C:\
and the databases are stored on a external drive array
i.e D:\
What i want to do is migrate the external drive array
from the above server to a new sql7 NT server of higher
spec.
Has anyone attempted this before or any ideas on how to
do this. I believe that i will have to start sql in
single user mode after the arrray is attached and run a
attach comand within query analyzer.
Any help would be much appreciated.You won't have to start the server in single-user mode... But you will have
to put the database in single-user mode to detach it (if that's how you
choose to get it over to the new server.) Your options are to detach it
from the old server, copy it, and re-attach it, or back it up and restore it
on the new server... Pretty much equivalent options except that backup will
double the disc space required (as you will have the database files as well
as the backup file to deal with); detach/attach, on the other hand, will
require you to A) put the database into single-user mode, and B) take it
offline while you copy the files, which you will not have to do with a
backup. So weigh your options carefully...
"Jonathan Gray" <jonathan.gray@.exel.com> wrote in message
news:0dbc01c3adda$7e102950$a101280a@.phx.gbl...
> Please consider the following scenario
> I have sql 7 NT server the application is on the C:\
> and the databases are stored on a external drive array
> i.e D:\
> What i want to do is migrate the external drive array
> from the above server to a new sql7 NT server of higher
> spec.
> Has anyone attempted this before or any ideas on how to
> do this. I believe that i will have to start sql in
> single user mode after the arrray is attached and run a
> attach comand within query analyzer.
>
> Any help would be much appreciated.

Wednesday, March 28, 2012

Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.0?
MCDBA 2000
MCSE 2000
Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/d...displaylang=en
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"G Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>
|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQL
Server 2005.
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:

> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at your
> SQL Server 2000 database, and have it scan it. The report and documentation
> are very comprehensive.
> http://www.microsoft.com/downloads/d...displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
>
>
|||On Mon, 13 Feb 2006 04:26:16 -0800, G Brander wrote:

>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?
Hi G,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
Hugo Kornelis, SQL Server MVP

Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.0?
--
MCDBA 2000
MCSE 2000Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/details.aspx?familyid=451FBF81-AB07-4CCB-A18B-DA38F6BCF484&displaylang=en
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQL
Server 2005.
--
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:
> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at your
> SQL Server 2000 database, and have it scan it. The report and documentation
> are very comprehensive.
> http://www.microsoft.com/downloads/details.aspx?familyid=451FBF81-AB07-4CCB-A18B-DA38F6BCF484&displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "GÃ© Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> > What sort of problems can I expect when moving my SQL 2000 databases to
> > the
> > SQL 2005 platform?
> >
> > Must there be an adaption of code for some of the objects (sp, view, udf
> > etc), or will it work fine when I put the database compatibility level to
> > 8.0?
> > --
> > MCDBA 2000
> > MCSE 2000
> >
>
>|||On Mon, 13 Feb 2006 04:26:16 -0800, Gé Brander wrote:
>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?
Hi Gé,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
--
Hugo Kornelis, SQL Server MVP

Migrating databases SQL 2000 to SQL 2005

What sort of problems can I expect when moving my SQL 2000 databases to the
SQL 2005 platform?
Must there be an adaption of code for some of the objects (sp, view, udf
etc), or will it work fine when I put the database compatibility level to 8.
0?
--
MCDBA 2000
MCSE 2000Everything that you need to know about upgrade issues with an existing
database can be found in the Upgrade Advisor. Download it, point it at your
SQL Server 2000 database, and have it scan it. The report and documentation
are very comprehensive.
http://www.microsoft.com/downloads/...&displaylang=en
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"G Brander" <GBrander@.discussions.microsoft.com> wrote in message
news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
> What sort of problems can I expect when moving my SQL 2000 databases to
> the
> SQL 2005 platform?
> Must there be an adaption of code for some of the objects (sp, view, udf
> etc), or will it work fine when I put the database compatibility level to
> 8.0?
> --
> MCDBA 2000
> MCSE 2000
>|||Thanks for your answer, but I am not talking about instances, but databases.
I want to migrate several SQL Server 2000 databases to a SQL Server 2005
database server. I do not want to upgrade my SQL Server 2000 instance tot SQ
L
Server 2005.
--
MCDBA 2000
MCSE 2000
"Michael Hotek" wrote:

> Everything that you need to know about upgrade issues with an existing
> database can be found in the Upgrade Advisor. Download it, point it at yo
ur
> SQL Server 2000 database, and have it scan it. The report and documentati
on
> are very comprehensive.
> http://www.microsoft.com/downloads/...&displaylang=en
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Gé Brander" <GBrander@.discussions.microsoft.com> wrote in message
> news:3AAD007C-0540-4948-A120-5136CC7D5BF4@.microsoft.com...
>
>|||On Mon, 13 Feb 2006 04:26:16 -0800, G Brander wrote:
[vbcol=seagreen]
>What sort of problems can I expect when moving my SQL 2000 databases to the
>SQL 2005 platform?
>Must there be an adaption of code for some of the objects (sp, view, udf
>etc), or will it work fine when I put the database compatibility level to 8.0?[/vbc
ol]
Hi G,
I just posted a reply to your question in the Dutch group
microsoft.public.nl.sql.
Hugo Kornelis, SQL Server MVP

migrating cluster instances to stand alone install

Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server.
Got several issues i'd like some advice on.

1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move.
I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance.
For example: cluster install is aiproddb\production, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work.
Does this seem like a reasonable approach?

2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.

3. what's the best way to transfer DTS packages?

4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?

5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?

Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.

thanks,
Garth:D 5. [...] Is the wizard for copying databases a good thing?

thanks,
Garth

NOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!

:D

hmscott|||ok. that's one vote against the copy database wizard...|||Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server.
Got several issues i'd like some advice on.

1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move.
I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance.

I know this does not help you now, but in the future, try adding a layer of virtualization in between by using a DNS zone specific to your apps. Then you can move physical servers in and out of production smoothly without impacting application connection strings. Use one DNS A record per database (e.g. MyDB.dev.apps, MySecondDB.dev.apps and MyDB.test.apps and MySecondDB.test.apps). The apps point to the DNS name, the DNS name translates to a physical IP. When it comes time to migrate a database (or an entire server) you have one place to go to update IP addresses (the DNS server).

2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.

Try exporting the logins to a file, cull selected logins that you don't want/need (sa comes to mind) and then inserting them with proper syntax. Somewhere there is an MS article about using BCP to do this. If I recall correctly, use "bcp log shipping sgl server logins" for your google. I also did it by copying and pasting into an Excel spreadsheet and then using formulae to build the SQL syntax. Crude, but it worked.

This will only build the logins and it will not link the users within the database to the logins (SID mismatch). For that you can use sp_change_users_login.

3. what's the best way to transfer DTS packages?

Depends on how much of your connection info is embedded. A while back I posted a script for backing up DTS packages to a structured file. If there aren't too many, this is a workable approach.

By the way, is this an upgrade to SQL 2005, or a lateral to another SQL 2000 instance? If the former, you have more work cut out for you. If the latter, you should really consider the former (ie, you should be working on an upgrade).

4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?

Should be all right. Watch the AWE memory thing with SP4, but I don't remember specific issues with SP4. Be careful if you are using replication.

5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way?

sp_detach and sp_attach?

The advantage with your method (if you have a large database) is that you can do a partial restore (which might take a long time) and then apply just the last log file to bring the new instance up to date to minimize your outage.

Is the wizard for copying databases a good thing?

Noooooooooooooooo!!!!!

But enough on that subject :D .

Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.

thanks,
Garth

Test, test, test, practice, practice, practice.

Good luck.

Regards,

hmscott

Migrating CLOBS and BLOBS to SQL SERVER from ORACLE 9i

I am taking over a Database set up where we have 2 databases. One is a SQL SERVER 2000 db and the other is an Oracle 9i db.

THe previous DBA had/has a problem with transferring CLOB and Blob datatypes From the ORACLE db to SQL SERVER. He says that the OLEDB driver SQL SERVER provides has limitations particularly on the CLOB data because it truncates data over 4000 characters in length.

For the Blob issue:
We basically want to store/move attachments (word documents etc)
into image datatypes (SS) from the blob datatype (9i).

I figured I could do this using DTS or even using the Linked server method. I figured worst case scenario I would just store the documents on the server and then use SQL SERVER's textcopy utility to upload the documents into the image datatype column of the SQL SERVER table.

For the Clob Issue I have no idea what to do, because I cant find anything online that mentions SQL SERVER having issues with importing CLOB data over 4000 charcters in length, afterall the text datatype accomdates more than 4000 characters.

Does anyone have any suggestions for moving the Blob and most importantly the Clob datatypes from 9i to SQL SERVER without any truncation in the data??Did you try the DTS approach?|||...and you realize this will retart the firestorm argument about whether it is better to store BLOBs in the database, or in the File System with a simple link in the database...|||I don't think there is a limitation. I usually do a BCP to load them in. Check out this site for some good stuff:

TEXT, NTEXT, and IMAGE datatypes - Tutorial (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro03/html/sp03g8.asp)|||Originally posted by bpdWork
...and you realize this will retart the firestorm argument about whether it is better to store BLOBs in the database, or in the File System with a simple link in the database...

I dont think DTS has an issue with migrating Blobs. It does have issues with migrating Clobs with data over 4000 characters in Length

p.s. LOL about starting a firestorm|||Originally posted by rdjabarov
I don't think there is a limitation. I usually do a BCP to load them in. Check out this site for some good stuff:

TEXT, NTEXT, and IMAGE datatypes - Tutorial (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro03/html/sp03g8.asp)

Thanks. Ill go through it

Monday, March 26, 2012

Migrating an SQL server to another machine

Hello,
I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
keep al the settings/users/databases intact.
How could this be acomplished?
Kind regards,
Paul.
One or more of below should get you started:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Paul" <microsoftnews@.knipsel.nl> wrote in message news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
> keep al the settings/users/databases intact.
> How could this be acomplished?
> Kind regards,
>
> Paul.
>
>
|||Thanks Tibor!
This will cetainly help!
Regards,
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OXnhJvIoEHA.3324@.TK2MSFTNGP10.phx.gbl...
> One or more of below should get you started:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
> Servers
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Paul" <microsoftnews@.knipsel.nl> wrote in message
> news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
>

Migrating an SQL server to another machine

Hello,
I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
keep al the settings/users/databases intact.
How could this be acomplished?
Kind regards,
Paul.One or more of below should get you started:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Paul" <microsoftnews@.knipsel.nl> wrote in message news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
> keep al the settings/users/databases intact.
> How could this be acomplished?
> Kind regards,
>
> Paul.
>
>|||Thanks Tibor!
This will cetainly help!
Regards,
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OXnhJvIoEHA.3324@.TK2MSFTNGP10.phx.gbl...
> One or more of below should get you started:
>
> Moving SQL Server Databases
> http://www.support.microsoft.com/?id=224071
> Moving Databases between Servers
> http://www.support.microsoft.com/?id=314546
> Using WITH MOVE in a Restore to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
> How to Resolve Permission Issues When a Database Is Moved Between SQL
> Servers
> http://www.support.microsoft.com/?id=240872
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Paul" <microsoftnews@.knipsel.nl> wrote in message
> news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
>> Hello,
>> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
>> keep al the settings/users/databases intact.
>> How could this be acomplished?
>> Kind regards,
>>
>> Paul.
>>
>>
>

Friday, March 23, 2012

Migrate two databases from diferente Server into one consolidate

Hi,
I have two servers running Sql-Server, recently we bought a new server to
consolidate the databases (The new server in must powerful that the oldest).
I Know how to backup and restore databases from one server to another, but I
dont know how to move the logins, some body know how I can move o backup
login from two servers and then restore in only one.
Thanks,
Mauricio CamposWhat i do is create the same login names on the new server, I then go and ru
n
this command after the restor is done. Then all i have to do is reset each
login with the correct default databases. Here's the command:
sp_configure 'Allow updates', 1
RECONFIGURE WITH OVERRIDE
go
begin
declare @.databasename varchar(50)
select @.databasename = 'Put your database name here'
declare @.statement varchar(255)
select @.statement = 'update '+ @.databasename + '.dbo.sysusers set sid = m.si
d
from master.dbo.syslogins m
where ' + @.databasename + '.dbo.sysusers.name = m.name'
execute (@.statement)
end
go
sp_configure 'Allow updates', 0
RECONFIGURE WITH OVERRIDE
go
Hope this helps
"Mauricio Campos" wrote:

> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the oldest
).
> I Know how to backup and restore databases from one server to another, but
I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos|||Hi,
Have a look into this article as well. Since you are populating the logins
from multiple sql servers you may need to do some manual sync using
sp_change_users_login system stored proc.
http://www.databasejournal.com/feat...cle.php/1438491
Thanks
Hari
SQL Server MVP
"Mauricio Campos" <MauricioCampos@.discussions.microsoft.com> wrote in
message news:17869C0F-FE6E-4E9D-BCBF-D59369A752C5@.microsoft.com...
> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the
> oldest).
> I Know how to backup and restore databases from one server to another, but
> I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos|||I've never gotten around to using it, but have a look at DTs - there is a
transfer login's task, I believe. Google / BOL it to get more detail (I'll
try and find somethings on it when I have a moment).
CiaO|||the problem with this task is that it doesn't keep the original SID. I prefe
r using sp_help_revlogin
which is fund in the KB.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Regan Galbraith via droptable.com" <forum@.droptable.com> wrote in message
news:052be1beaac14f44905f5fe6eaf03ab1@.SQ
droptable.com...
> I've never gotten around to using it, but have a look at DTs - there is a
> transfer login's task, I believe. Google / BOL it to get more detail (I'll
> try and find somethings on it when I have a moment).
> CiaO|||Also, the DTS transfer logins task doesn't copy across the passwords.
The technique that I've used successfully in the past many times is a bit
fiddly but gives 100% success:
1. Use either a transfer logins task or SQLEM scripting to create logins
on the new server.
2. Use DTS to copy the sysxlogins table to a separate database on the new
server - we used to use Northwind
3. In the same DTS, run a looped statement to directly update the system
tables on the new server, overwriting the blank passwords with the
encrypted versions (don't forget to include a step to delete the temporary
table afterwards).
All the logins should now be on the server, but as Tibor pointed out, they
have new SIDs which will not match those in any restored databases.
4. In each restored database, run another 'fixusers' SP which we adapted
from some code on a forum several years ago to sync the SIDs (matches
logins by name only)
All of this is obviously quite risky, as you are directly updating system
tables, and I would only recommend this to be carried out on a non-
production server. It works for SQL7.x and 2000 but will not be possible
on SQL2005 due to the system tables being hidden.
I can include the SP code if required, but didn't want to bloat the posting
unnecessarily. Not sure if its possible to include the DTS as an
attachment, but it's fairly straigthforward anyway.
HTH
Andy H
Message posted via http://www.droptable.com|||Andy,
I'm curious... Is there a reason you don't use sp_help_revlogins?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via droptable.com" <forum@.droptable.com> wrote in message
news:ec6f8ddb169e4892bac0f4d0c24c539e@.SQ
droptable.com...
> Also, the DTS transfer logins task doesn't copy across the passwords.
> The technique that I've used successfully in the past many times is a bit
> fiddly but gives 100% success:
> 1. Use either a transfer logins task or SQLEM scripting to create logins
> on the new server.
> 2. Use DTS to copy the sysxlogins table to a separate database on the new
> server - we used to use Northwind
> 3. In the same DTS, run a looped statement to directly update the system
> tables on the new server, overwriting the blank passwords with the
> encrypted versions (don't forget to include a step to delete the temporary
> table afterwards).
> All the logins should now be on the server, but as Tibor pointed out, they
> have new SIDs which will not match those in any restored databases.
> 4. In each restored database, run another 'fixusers' SP which we adapted
> from some code on a forum several years ago to sync the SIDs (matches
> logins by name only)
>
> All of this is obviously quite risky, as you are directly updating system
> tables, and I would only recommend this to be carried out on a non-
> production server. It works for SQL7.x and 2000 but will not be possible
> on SQL2005 due to the system tables being hidden.
> I can include the SP code if required, but didn't want to bloat the postin
g
> unnecessarily. Not sure if its possible to include the DTS as an
> attachment, but it's fairly straigthforward anyway.
> HTH
> Andy H
> --
> Message posted via http://www.droptable.com|||Tibor
Ignorance is my only excuse ;-)
You know how it goes - if it isn't broken, why fix it. This process was
developed in the early days of SQL 7 and DTS through necessity and
continued to work well on SQL 2000. I'd missed the publication of this KB
article. A much better way of doing things.
Thanks for the info.
To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
Regards
Andy
Message posted via http://www.droptable.com|||Andy,

> You know how it goes - if it isn't broken, why fix it.
Sure do :-). I was just curious whether you had found significant upsides co
mpared to
sp_help_revlogins...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via droptable.com" <forum@.droptable.com> wrote in message
news:20a0eede24724d2681acf9129d27fc7d@.SQ
droptable.com...
> Tibor
> Ignorance is my only excuse ;-)
> You know how it goes - if it isn't broken, why fix it. This process was
> developed in the early days of SQL 7 and DTS through necessity and
> continued to work well on SQL 2000. I'd missed the publication of this KB
> article. A much better way of doing things.
> Thanks for the info.
> To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
> Regards
> Andy
> --
> Message posted via http://www.droptable.com

Migrate two databases from diferente Server into one consolidate

Hi,
I have two servers running Sql-Server, recently we bought a new server to
consolidate the databases (The new server in must powerful that the oldest).
I Know how to backup and restore databases from one server to another, but I
dont know how to move the logins, some body know how I can move o backup
login from two servers and then restore in only one.
Thanks,
Mauricio Campos
What i do is create the same login names on the new server, I then go and run
this command after the restor is done. Then all i have to do is reset each
login with the correct default databases. Here's the command:
sp_configure 'Allow updates', 1
RECONFIGURE WITH OVERRIDE
go
begin
declare @.databasename varchar(50)
select @.databasename = 'Put your database name here'
declare @.statement varchar(255)
select @.statement = 'update '+ @.databasename + '.dbo.sysusers set sid = m.sid
from master.dbo.syslogins m
where ' + @.databasename + '.dbo.sysusers.name = m.name'
execute (@.statement)
end
go
sp_configure 'Allow updates', 0
RECONFIGURE WITH OVERRIDE
go
Hope this helps
"Mauricio Campos" wrote:

> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the oldest).
> I Know how to backup and restore databases from one server to another, but I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos
|||Hi,
Have a look into this article as well. Since you are populating the logins
from multiple sql servers you may need to do some manual sync using
sp_change_users_login system stored proc.
http://www.databasejournal.com/featu...le.php/1438491
Thanks
Hari
SQL Server MVP
"Mauricio Campos" <MauricioCampos@.discussions.microsoft.com> wrote in
message news:17869C0F-FE6E-4E9D-BCBF-D59369A752C5@.microsoft.com...
> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the
> oldest).
> I Know how to backup and restore databases from one server to another, but
> I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos
|||I've never gotten around to using it, but have a look at DTs - there is a
transfer login's task, I believe. Google / BOL it to get more detail (I'll
try and find somethings on it when I have a moment).
CiaO
|||the problem with this task is that it doesn't keep the original SID. I prefer using sp_help_revlogin
which is fund in the KB.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Regan Galbraith via droptable.com" <forum@.droptable.com> wrote in message
news:052be1beaac14f44905f5fe6eaf03ab1@.droptable.co m...
> I've never gotten around to using it, but have a look at DTs - there is a
> transfer login's task, I believe. Google / BOL it to get more detail (I'll
> try and find somethings on it when I have a moment).
> CiaO
|||Also, the DTS transfer logins task doesn't copy across the passwords.
The technique that I've used successfully in the past many times is a bit
fiddly but gives 100% success:
1. Use either a transfer logins task or SQLEM scripting to create logins
on the new server.
2. Use DTS to copy the sysxlogins table to a separate database on the new
server - we used to use Northwind
3. In the same DTS, run a looped statement to directly update the system
tables on the new server, overwriting the blank passwords with the
encrypted versions (don't forget to include a step to delete the temporary
table afterwards).
All the logins should now be on the server, but as Tibor pointed out, they
have new SIDs which will not match those in any restored databases.
4. In each restored database, run another 'fixusers' SP which we adapted
from some code on a forum several years ago to sync the SIDs (matches
logins by name only)
All of this is obviously quite risky, as you are directly updating system
tables, and I would only recommend this to be carried out on a non-
production server. It works for SQL7.x and 2000 but will not be possible
on SQL2005 due to the system tables being hidden.
I can include the SP code if required, but didn't want to bloat the posting
unnecessarily. Not sure if its possible to include the DTS as an
attachment, but it's fairly straigthforward anyway.
HTH
Andy H
Message posted via http://www.droptable.com
|||Andy,
I'm curious... Is there a reason you don't use sp_help_revlogins?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via droptable.com" <forum@.droptable.com> wrote in message
news:ec6f8ddb169e4892bac0f4d0c24c539e@.droptable.co m...
> Also, the DTS transfer logins task doesn't copy across the passwords.
> The technique that I've used successfully in the past many times is a bit
> fiddly but gives 100% success:
> 1. Use either a transfer logins task or SQLEM scripting to create logins
> on the new server.
> 2. Use DTS to copy the sysxlogins table to a separate database on the new
> server - we used to use Northwind
> 3. In the same DTS, run a looped statement to directly update the system
> tables on the new server, overwriting the blank passwords with the
> encrypted versions (don't forget to include a step to delete the temporary
> table afterwards).
> All the logins should now be on the server, but as Tibor pointed out, they
> have new SIDs which will not match those in any restored databases.
> 4. In each restored database, run another 'fixusers' SP which we adapted
> from some code on a forum several years ago to sync the SIDs (matches
> logins by name only)
>
> All of this is obviously quite risky, as you are directly updating system
> tables, and I would only recommend this to be carried out on a non-
> production server. It works for SQL7.x and 2000 but will not be possible
> on SQL2005 due to the system tables being hidden.
> I can include the SP code if required, but didn't want to bloat the posting
> unnecessarily. Not sure if its possible to include the DTS as an
> attachment, but it's fairly straigthforward anyway.
> HTH
> Andy H
> --
> Message posted via http://www.droptable.com
|||Tibor
Ignorance is my only excuse ;-)
You know how it goes - if it isn't broken, why fix it. This process was
developed in the early days of SQL 7 and DTS through necessity and
continued to work well on SQL 2000. I'd missed the publication of this KB
article. A much better way of doing things.
Thanks for the info.
To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
Regards
Andy
Message posted via http://www.droptable.com
|||Andy,

> You know how it goes - if it isn't broken, why fix it.
Sure do :-). I was just curious whether you had found significant upsides compared to
sp_help_revlogins...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via droptable.com" <forum@.droptable.com> wrote in message
news:20a0eede24724d2681acf9129d27fc7d@.droptable.co m...
> Tibor
> Ignorance is my only excuse ;-)
> You know how it goes - if it isn't broken, why fix it. This process was
> developed in the early days of SQL 7 and DTS through necessity and
> continued to work well on SQL 2000. I'd missed the publication of this KB
> article. A much better way of doing things.
> Thanks for the info.
> To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
> Regards
> Andy
> --
> Message posted via http://www.droptable.com

Migrate two databases from diferente Server into one consolidate

Hi,
I have two servers running Sql-Server, recently we bought a new server to
consolidate the databases (The new server in must powerful that the oldest).
I Know how to backup and restore databases from one server to another, but I
dont know how to move the logins, some body know how I can move o backup
login from two servers and then restore in only one.
Thanks,
Mauricio CamposWhat i do is create the same login names on the new server, I then go and run
this command after the restor is done. Then all i have to do is reset each
login with the correct default databases. Here's the command:
sp_configure 'Allow updates', 1
RECONFIGURE WITH OVERRIDE
go
begin
declare @.databasename varchar(50)
select @.databasename = 'Put your database name here'
declare @.statement varchar(255)
select @.statement = 'update '+ @.databasename + '.dbo.sysusers set sid = m.sid
from master.dbo.syslogins m
where ' + @.databasename + '.dbo.sysusers.name = m.name'
execute (@.statement)
end
go
sp_configure 'Allow updates', 0
RECONFIGURE WITH OVERRIDE
go
Hope this helps
"Mauricio Campos" wrote:
> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the oldest).
> I Know how to backup and restore databases from one server to another, but I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos|||Hi,
Have a look into this article as well. Since you are populating the logins
from multiple sql servers you may need to do some manual sync using
sp_change_users_login system stored proc.
http://www.databasejournal.com/features/mssql/article.php/1438491
Thanks
Hari
SQL Server MVP
"Mauricio Campos" <MauricioCampos@.discussions.microsoft.com> wrote in
message news:17869C0F-FE6E-4E9D-BCBF-D59369A752C5@.microsoft.com...
> Hi,
> I have two servers running Sql-Server, recently we bought a new server to
> consolidate the databases (The new server in must powerful that the
> oldest).
> I Know how to backup and restore databases from one server to another, but
> I
> dont know how to move the logins, some body know how I can move o backup
> login from two servers and then restore in only one.
> Thanks,
> Mauricio Campos|||I've never gotten around to using it, but have a look at DTs - there is a
transfer login's task, I believe. Google / BOL it to get more detail (I'll
try and find somethings on it when I have a moment).
CiaO|||the problem with this task is that it doesn't keep the original SID. I prefer using sp_help_revlogin
which is fund in the KB.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Regan Galbraith via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:052be1beaac14f44905f5fe6eaf03ab1@.SQLMonster.com...
> I've never gotten around to using it, but have a look at DTs - there is a
> transfer login's task, I believe. Google / BOL it to get more detail (I'll
> try and find somethings on it when I have a moment).
> CiaO|||Also, the DTS transfer logins task doesn't copy across the passwords.
The technique that I've used successfully in the past many times is a bit
fiddly but gives 100% success:
1. Use either a transfer logins task or SQLEM scripting to create logins
on the new server.
2. Use DTS to copy the sysxlogins table to a separate database on the new
server - we used to use Northwind
3. In the same DTS, run a looped statement to directly update the system
tables on the new server, overwriting the blank passwords with the
encrypted versions (don't forget to include a step to delete the temporary
table afterwards).
All the logins should now be on the server, but as Tibor pointed out, they
have new SIDs which will not match those in any restored databases.
4. In each restored database, run another 'fixusers' SP which we adapted
from some code on a forum several years ago to sync the SIDs (matches
logins by name only)
All of this is obviously quite risky, as you are directly updating system
tables, and I would only recommend this to be carried out on a non-
production server. It works for SQL7.x and 2000 but will not be possible
on SQL2005 due to the system tables being hidden.
I can include the SP code if required, but didn't want to bloat the posting
unnecessarily. Not sure if its possible to include the DTS as an
attachment, but it's fairly straigthforward anyway.
HTH
Andy H
--
Message posted via http://www.sqlmonster.com|||Andy,
I'm curious... Is there a reason you don't use sp_help_revlogins?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:ec6f8ddb169e4892bac0f4d0c24c539e@.SQLMonster.com...
> Also, the DTS transfer logins task doesn't copy across the passwords.
> The technique that I've used successfully in the past many times is a bit
> fiddly but gives 100% success:
> 1. Use either a transfer logins task or SQLEM scripting to create logins
> on the new server.
> 2. Use DTS to copy the sysxlogins table to a separate database on the new
> server - we used to use Northwind
> 3. In the same DTS, run a looped statement to directly update the system
> tables on the new server, overwriting the blank passwords with the
> encrypted versions (don't forget to include a step to delete the temporary
> table afterwards).
> All the logins should now be on the server, but as Tibor pointed out, they
> have new SIDs which will not match those in any restored databases.
> 4. In each restored database, run another 'fixusers' SP which we adapted
> from some code on a forum several years ago to sync the SIDs (matches
> logins by name only)
>
> All of this is obviously quite risky, as you are directly updating system
> tables, and I would only recommend this to be carried out on a non-
> production server. It works for SQL7.x and 2000 but will not be possible
> on SQL2005 due to the system tables being hidden.
> I can include the SP code if required, but didn't want to bloat the posting
> unnecessarily. Not sure if its possible to include the DTS as an
> attachment, but it's fairly straigthforward anyway.
> HTH
> Andy H
> --
> Message posted via http://www.sqlmonster.com|||Tibor
Ignorance is my only excuse ;-)
You know how it goes - if it isn't broken, why fix it. This process was
developed in the early days of SQL 7 and DTS through necessity and
continued to work well on SQL 2000. I'd missed the publication of this KB
article. A much better way of doing things.
Thanks for the info.
To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
Regards
Andy
--
Message posted via http://www.sqlmonster.com|||Andy,
> You know how it goes - if it isn't broken, why fix it.
Sure do :-). I was just curious whether you had found significant upsides compared to
sp_help_revlogins...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy Hughes via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:20a0eede24724d2681acf9129d27fc7d@.SQLMonster.com...
> Tibor
> Ignorance is my only excuse ;-)
> You know how it goes - if it isn't broken, why fix it. This process was
> developed in the early days of SQL 7 and DTS through necessity and
> continued to work well on SQL 2000. I'd missed the publication of this KB
> article. A much better way of doing things.
> Thanks for the info.
> To save Mauricio some time: http://support.microsoft.com/kb/246133/#5
> Regards
> Andy
> --
> Message posted via http://www.sqlmonster.comsql

Migrate SQL Server 2000 to SQL Server 2005: login

Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin

> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>|||Check out:
http://support.microsoft.com/defaul...kb;en-us;246133
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:ejLryIm1GHA.4264@.TK2MSFTNGP05.phx.gbl...
Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)|||The best way to do this is to transfer the logins with sp_help_revlogin to a
clean server - i.e. one with no logins. Do this just before you want to cut
over or advise your users that their password won't be current on the new
box if they change their passwords on the old box after you've transferred
them. You won't need sp_change_users_login in that case.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:%23Xf$aNm1GHA.4908@.TK2MSFTNGP02.phx.gbl...
Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin

> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>

Migrate SQL Server 2000 to SQL Server 2005: login

Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin
> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>|||Check out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:ejLryIm1GHA.4264@.TK2MSFTNGP05.phx.gbl...
Hi!
I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
Server 2005 and have had some problems with the logins and users, so I
wonder which is the "correct" way to make it right =)|||The best way to do this is to transfer the logins with sp_help_revlogin to a
clean server - i.e. one with no logins. Do this just before you want to cut
over or advise your users that their password won't be current on the new
box if they change their passwords on the old box after you've transferred
them. You won't need sp_change_users_login in that case.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Malin Davidsson" <malin.davidsson(at)aus.teleca.se> wrote in message
news:%23Xf$aNm1GHA.4908@.TK2MSFTNGP02.phx.gbl...
Ooops, I hit send accidently and sent this message before I was done with
it. =)
Here's the continuation:
So far I have used sp_help_revlogin and after that sp_change_users_login,
but the password for a login was wrong after this. Is there something else I
should do?
Thanks
//Malin
> Hi!
> I'm trying to migrate (side-by-side) databases from SQL Server 2000 to SQL
> Server 2005 and have had some problems with the logins and users, so I
> wonder which is the "correct" way to make it right =)
>sql

Wednesday, March 21, 2012

migrate server to another machine

Hi,
I will migrate the databases using the Microsoft SQL Database Migration
Wizard to another machine.
Can(how) I keep the same all username and password and data?
Usually hwo to do that? Thanks.http://databasejournal.com/features/mssql/article.php/2228611
That should get you what you need.
--
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"js@.someone.com" wrote:
> Hi,
> I will migrate the databases using the Microsoft SQL Database Migration
> Wizard to another machine.
> Can(how) I keep the same all username and password and data?
> Usually hwo to do that? Thanks.
>
>|||Thanks for the help.
Can Microsoft SQL Database Migration Wizard used for
migration?
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
> http://databasejournal.com/features/mssql/article.php/2228611
> That should get you what you need.
> --
> MeanOldDBA
> derrickleggett@.hotmail.com
> http://weblogs.sqlteam.com/derrickl
> When life gives you a lemon, fire the DBA.
>
> "js@.someone.com" wrote:
>> Hi,
>> I will migrate the databases using the Microsoft SQL Database Migration
>> Wizard to another machine.
>> Can(how) I keep the same all username and password and data?
>> Usually hwo to do that? Thanks.
>>|||Hi,
The simplest way u can migrate ur database and logins are
restore the backup on the other server and trabfer all the logins from
dts package.
yes u can use microsoft migration wizard for migration.
from
Doller
js@.someone.com wrote:
> Thanks for the help.
> Can Microsoft SQL Database Migration Wizard used for
> migration?
>
> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
> > http://databasejournal.com/features/mssql/article.php/2228611
> >
> > That should get you what you need.
> > --
> > MeanOldDBA
> > derrickleggett@.hotmail.com
> > http://weblogs.sqlteam.com/derrickl
> >
> > When life gives you a lemon, fire the DBA.
> >
> >
> > "js@.someone.com" wrote:
> >
> >> Hi,
> >> I will migrate the databases using the Microsoft SQL Database Migration
> >> Wizard to another machine.
> >> Can(how) I keep the same all username and password and data?
> >>
> >> Usually hwo to do that? Thanks.
> >>
> >>
> >>|||>> yes u can use microsoft migration wizard for migration.
Thanks, using migration wizard will auto keep the logins?
"doller" <sufianarif@.gmail.com> wrote in message
news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
> Hi,
> The simplest way u can migrate ur database and logins are
> restore the backup on the other server and trabfer all the logins from
> dts package.
> yes u can use microsoft migration wizard for migration.
> from
> Doller
>
> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>> > http://databasejournal.com/features/mssql/article.php/2228611
>> >
>> > That should get you what you need.
>> > --
>> > MeanOldDBA
>> > derrickleggett@.hotmail.com
>> > http://weblogs.sqlteam.com/derrickl
>> >
>> > When life gives you a lemon, fire the DBA.
>> >
>> >
>> > "js@.someone.com" wrote:
>> >
>> >> Hi,
>> >> I will migrate the databases using the Microsoft SQL Database
>> >> Migration
>> >> Wizard to another machine.
>> >> Can(how) I keep the same all username and password and data?
>> >>
>> >> Usually hwo to do that? Thanks.
>> >>
>> >>
>> >>
>|||Can you tell use exactly what "database migration wizard" is found. I don't have such tool on my SQL
Server 2000 installation. Do you refer to the "Copy Database Wizard"?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"js" <js@.someone@.hotmail.com> wrote in message news:OIuy1XOyFHA.1132@.TK2MSFTNGP10.phx.gbl...
>> yes u can use microsoft migration wizard for migration.
> Thanks, using migration wizard will auto keep the logins?
>
> "doller" <sufianarif@.gmail.com> wrote in message
> news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
>> Hi,
>> The simplest way u can migrate ur database and logins are
>> restore the backup on the other server and trabfer all the logins from
>> dts package.
>> yes u can use microsoft migration wizard for migration.
>> from
>> Doller
>>
>> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>> > http://databasejournal.com/features/mssql/article.php/2228611
>> >
>> > That should get you what you need.
>> > --
>> > MeanOldDBA
>> > derrickleggett@.hotmail.com
>> > http://weblogs.sqlteam.com/derrickl
>> >
>> > When life gives you a lemon, fire the DBA.
>> >
>> >
>> > "js@.someone.com" wrote:
>> >
>> >> Hi,
>> >> I will migrate the databases using the Microsoft SQL Database Migration
>> >> Wizard to another machine.
>> >> Can(how) I keep the same all username and password and data?
>> >>
>> >> Usually hwo to do that? Thanks.
>> >>
>> >>
>> >>
>|||I don't know other tools, but found "Copy Database Wizard".
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23v2vNKQyFHA.2880@.TK2MSFTNGP12.phx.gbl...
> Can you tell use exactly what "database migration wizard" is found. I
> don't have such tool on my SQL Server 2000 installation. Do you refer to
> the "Copy Database Wizard"?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "js" <js@.someone@.hotmail.com> wrote in message
> news:OIuy1XOyFHA.1132@.TK2MSFTNGP10.phx.gbl...
>> yes u can use microsoft migration wizard for migration.
>> Thanks, using migration wizard will auto keep the logins?
>>
>> "doller" <sufianarif@.gmail.com> wrote in message
>> news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
>> Hi,
>> The simplest way u can migrate ur database and logins are
>> restore the backup on the other server and trabfer all the logins from
>> dts package.
>> yes u can use microsoft migration wizard for migration.
>> from
>> Doller
>>
>> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>> > http://databasejournal.com/features/mssql/article.php/2228611
>> >
>> > That should get you what you need.
>> > --
>> > MeanOldDBA
>> > derrickleggett@.hotmail.com
>> > http://weblogs.sqlteam.com/derrickl
>> >
>> > When life gives you a lemon, fire the DBA.
>> >
>> >
>> > "js@.someone.com" wrote:
>> >
>> >> Hi,
>> >> I will migrate the databases using the Microsoft SQL Database
>> >> Migration
>> >> Wizard to another machine.
>> >> Can(how) I keep the same all username and password and data?
>> >>
>> >> Usually hwo to do that? Thanks.
>> >>
>> >>
>> >>
>>
>|||I'm confused. You referred to a tool named "Data Migration Wizard". Are you now saying that the tool
you meant is actually the "Copy Database Wizard"?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"js" <js@.someone@.hotmail.com> wrote in message news:OlKQjWRyFHA.2072@.TK2MSFTNGP14.phx.gbl...
>I don't know other tools, but found "Copy Database Wizard".
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23v2vNKQyFHA.2880@.TK2MSFTNGP12.phx.gbl...
>> Can you tell use exactly what "database migration wizard" is found. I don't have such tool on my
>> SQL Server 2000 installation. Do you refer to the "Copy Database Wizard"?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "js" <js@.someone@.hotmail.com> wrote in message news:OIuy1XOyFHA.1132@.TK2MSFTNGP10.phx.gbl...
>> yes u can use microsoft migration wizard for migration.
>> Thanks, using migration wizard will auto keep the logins?
>>
>> "doller" <sufianarif@.gmail.com> wrote in message
>> news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
>> Hi,
>> The simplest way u can migrate ur database and logins are
>> restore the backup on the other server and trabfer all the logins from
>> dts package.
>> yes u can use microsoft migration wizard for migration.
>> from
>> Doller
>>
>> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>> > http://databasejournal.com/features/mssql/article.php/2228611
>> >
>> > That should get you what you need.
>> > --
>> > MeanOldDBA
>> > derrickleggett@.hotmail.com
>> > http://weblogs.sqlteam.com/derrickl
>> >
>> > When life gives you a lemon, fire the DBA.
>> >
>> >
>> > "js@.someone.com" wrote:
>> >
>> >> Hi,
>> >> I will migrate the databases using the Microsoft SQL Database Migration
>> >> Wizard to another machine.
>> >> Can(how) I keep the same all username and password and data?
>> >>
>> >> Usually hwo to do that? Thanks.
>> >>
>> >>
>> >>
>>
>>
>|||js wrote:
> I don't know other tools, but found "Copy Database Wizard".
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23v2vNKQyFHA.2880@.TK2MSFTNGP12.phx.gbl...
>> Can you tell use exactly what "database migration wizard" is found. I
>> don't have such tool on my SQL Server 2000 installation. Do you refer to
>> the "Copy Database Wizard"?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "js" <js@.someone@.hotmail.com> wrote in message
>> news:OIuy1XOyFHA.1132@.TK2MSFTNGP10.phx.gbl...
>> yes u can use microsoft migration wizard for migration.
>> Thanks, using migration wizard will auto keep the logins?
>>
>> "doller" <sufianarif@.gmail.com> wrote in message
>> news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
>> Hi,
>> The simplest way u can migrate ur database and logins are
>> restore the backup on the other server and trabfer all the logins from
>> dts package.
>> yes u can use microsoft migration wizard for migration.
>> from
>> Doller
>>
>> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>> http://databasejournal.com/features/mssql/article.php/2228611
>> That should get you what you need.
>> --
>> MeanOldDBA
>> derrickleggett@.hotmail.com
>> http://weblogs.sqlteam.com/derrickl
>> When life gives you a lemon, fire the DBA.
>>
>> "js@.someone.com" wrote:
>>> Hi,
>>> I will migrate the databases using the Microsoft SQL Database
>>> Migration
>>> Wizard to another machine.
>>> Can(how) I keep the same all username and password and data?
>>>
>>> Usually hwo to do that? Thanks.
>>>
>>>
>>>
>
You can look up the description of the "Copy Database Wizard" in Books
On Line. It says that in addition to copying the actual databases, it
can also copy metadata like logins etc.
Regards
Steen|||> You can look up the description of the "Copy Database Wizard" in Books On Line. It says that in
> addition to copying the actual databases, it can also copy metadata like logins etc.
The reason I want to be certain what tool is referred to is that Copy Database Wizard does not carry
SID for SQL Server logins. So instead of letting CDW carry over logins, you use sp_help_revlogins
which will keep both password as well as SID for SQL server logins.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:%2333kVZYyFHA.596@.TK2MSFTNGP12.phx.gbl...
> js wrote:
>> I don't know other tools, but found "Copy Database Wizard".
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%23v2vNKQyFHA.2880@.TK2MSFTNGP12.phx.gbl...
>> Can you tell use exactly what "database migration wizard" is found. I don't have such tool on my
>> SQL Server 2000 installation. Do you refer to the "Copy Database Wizard"?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "js" <js@.someone@.hotmail.com> wrote in message news:OIuy1XOyFHA.1132@.TK2MSFTNGP10.phx.gbl...
>> yes u can use microsoft migration wizard for migration.
>> Thanks, using migration wizard will auto keep the logins?
>>
>> "doller" <sufianarif@.gmail.com> wrote in message
>> news:1128420204.497530.42080@.g14g2000cwa.googlegroups.com...
>> Hi,
>> The simplest way u can migrate ur database and logins are
>> restore the backup on the other server and trabfer all the logins from
>> dts package.
>> yes u can use microsoft migration wizard for migration.
>> from
>> Doller
>>
>> js@.someone.com wrote:
>> Thanks for the help.
>> Can Microsoft SQL Database Migration Wizard used for
>> migration?
>>
>> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
>> news:52EBC31B-6988-48E7-AD51-8E072A9B061C@.microsoft.com...
>>> http://databasejournal.com/features/mssql/article.php/2228611
>>>
>>> That should get you what you need.
>>> --
>>> MeanOldDBA
>>> derrickleggett@.hotmail.com
>>> http://weblogs.sqlteam.com/derrickl
>>>
>>> When life gives you a lemon, fire the DBA.
>>>
>>>
>>> "js@.someone.com" wrote:
>>>
>>> Hi,
>>> I will migrate the databases using the Microsoft SQL Database Migration
>>> Wizard to another machine.
>>> Can(how) I keep the same all username and password and data?
>>>
>>> Usually hwo to do that? Thanks.
>>>
>>>
>>>
>>
> You can look up the description of the "Copy Database Wizard" in Books On Line. It says that in
> addition to copying the actual databases, it can also copy metadata like logins etc.
> Regards
> Steensql

migrate server to another machine

Migrate Roles

Hi,
I need to migrate all databases from one server to another
existing database server, at this time i know how to
migrate all users logins avoiding orphaned users but i
dont know how to migrate all existing roles and how to
assign logins to existing Server Roles on the destination
with the minimum effort.
Best regards
Hi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/featu...le.php/2228611
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards
|||Hi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/featu...le.php/2228611
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards
|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards

>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/featu...l/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
another[vbcol=seagreen]
destination
>
>.
>
|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards

>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/featu...l/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
another[vbcol=seagreen]
destination
>
>.
>
|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...[vbcol=seagreen]
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> wide fixed roles also
> provide a easy method to
> with same id and
> 2228611
> message
> another
> destination
|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...[vbcol=seagreen]
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> wide fixed roles also
> provide a easy method to
> with same id and
> 2228611
> message
> another
> destination

Friday, March 30, 2012

migrating from Access to SQL Server

Migrating ext drive array

Wednesday, March 28, 2012

Migrating databases SQL 2000 to SQL 2005

Migrating databases SQL 2000 to SQL 2005

Migrating databases SQL 2000 to SQL 2005

migrating cluster instances to stand alone install

Migrating CLOBS and BLOBS to SQL SERVER from ORACLE 9i

Monday, March 26, 2012

Migrating an SQL server to another machine

Migrating an SQL server to another machine

Friday, March 23, 2012

Migrate two databases from diferente Server into one consolidate

Migrate two databases from diferente Server into one consolidate

Migrate two databases from diferente Server into one consolidate

Migrate SQL Server 2000 to SQL Server 2005: login

Migrate SQL Server 2000 to SQL Server 2005: login

Wednesday, March 21, 2012

migrate server to another machine

migrate server to another machine

migrate server to another machine

Migrate Roles

SQL Server Management Studio

Blog Archive

About Me