Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

http://msdn2.microsoft.com/en-us/library/ms137870.aspx

Set Task Properties

http://msdn2.microsoft.com/en-us/library/ms139733.aspx

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

http://msdn2.microsoft.com/en-us/library/ms137870.aspx

Set Task Properties

http://msdn2.microsoft.com/en-us/library/ms139733.aspx

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

http://msdn2.microsoft.com/en-us/library/ms137870.aspx

Set Task Properties

http://msdn2.microsoft.com/en-us/library/ms139733.aspx

/Anders

Mirroring and orphaned users

Hi there!

There is still a problem with mirrored (mapped) SQL Users. If you mirror a database where an application connects with an sql user, the mapping (login / user) will be lost on the mirror server. After a failover occurs, it it not possible to log onto the new principal database because the database use will be an orphaned user and has to be remapped to the login (using sp_change_users_login 'update_one', 'user', 'user').

Is there any chance to do it in a system trigger? What is the firing event after the failover occurs? I've tried something like following, but it doesn't fire.

alter TRIGGER map_orphaned_users

ON ALL SERVER

FOR ALTER_DATABASE

AS

execute sp_change_users_login 'update_one', 'easyris_41', 'easyris_41';

Someone an idea how to automate these usermapping after failover on the (new) principal server?

Based on:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mirroringevents.mspx#EDBAC

you can be set up to be notified (or run a job or particular sp) when the server becomes the principal.

Thanks,

mark

|||

Hmm, maybe thats a workaround.

But in my mind it doesn't confirm with the requirement of high availability with automatic failover. Furthermore, clients application could run into another exception (Login fails or something like that), what has to be adapted in applications what are designed for high avilibility.

Otherway all the stuff works with domain users. So it seems like a real bug. I can't see any conceptional reason for this behavior. Hope that will be fixed in SP2...

Torsten

|||

OK, I am going to try to write a bit.

1. I completely agree that from a customer's point of view, if when using sql logins, if the database fails over and the clients cannot get to the database (for whatever reason. Here it is a mixed mapping from login on a different server to a user in a "new" database ), then the system is not "highly available." So, we haven't made it easy to use mirroring in certain scenarios. I may try to create a script that solves this problem this weekend.

2. On the other hand, this problem has been here at least since 7.0. In log shipping, backup/restore, and attach/detach this problem of moving the database to a different server where the meta data in master and msdb are different on different servers. The problem is that we have made moving a database to a different server so much easier that the problems that were small earlier are becoming bigger.

So, this really isn't a bug IMHO, but it is unexpected behavior (which is still bad from a customer's point of view).

Thanks,

Mark

|||I am just starting to look into mirroring and had run across this same problem. I have not had a chance to look into this but supposedly there is a task in SSIS that allows you to transfer logins from one server to another.
|||

Hi guys,

I've asked MS about using sqlusers on a mirrored database and got this reply from Hugo Nunes, support Engineer at Microsoft.

In order to avoid orphaned users on the mirror database you’ll have to copy the logins corresponding to the database users, to the standby server. The copy must be made before restoring the database on the standby server. You’ll also need to copy the user with his SID. The Transfer Logins Task from SSIS performs that task for you as long you set the CopySids property to true.

It works.

|||

yes. but it doesn't solve the issue of default database for a login,

which leads to the same issue - login does not work.

|||

Hi to All,

We are currently having issues like that before, the fix that we do is adding a short dynamic script that will remove orphaned user by executing sp_change_users_login 'update_one', '<user1>','<user1>' on the mirrored database everytime a switch occur.

hope this helps!

regards,

|||

Hi Anders,

Did you ever got this to work? Do you know of any documents that walk you thought on how to do this? I am new with SSIS.

Thanks

Rick

|||

Hi Rick,

Yes, it's been up and running for almost a year now.

Im sorry i dont have a walk through for you but the SSIS bit is pretty straight forward.

These documents should get you started.

Transfer Logins Task

http://msdn2.microsoft.com/en-us/library/ms137870.aspx

Set Task Properties

http://msdn2.microsoft.com/en-us/library/ms139733.aspx

/Anders

Migrating to a new server

I currently have SQL running on an server that used to be used for call
center operations. There are many orphaned applications on this server and
we are planning to back up the server, reinstall a freash copy of 2000 server
and SQL 2000.
I have seen there is several ways to migrate data back onto the server,
detach / attach, restore from back up's, etc...
Our data center who is responsible for the maintenance of the server uses a
tool called vertias to back up the SQL databases.
Can anyone tell me the best method of restoring the system?Hi Gary
Usually it will depend on how big the databases are as to how you plan this.
You don't say if you normally back your databases up to disc and then to tape
or use the plug-ins. You also don't say if you are going to reformat the
drives or not!
If you backup to disc then you can use those backups to restore the
databases, providing the drives have not been reformated! If you don't have
backups on disc you could backup to a networked machine or possibly a plugged
in device and then use them to restore from. Restoring from tape will be
possible, but it will probably take significantly longer. You should also
verify the backups (tape or disc) before you remove SQL Server. As an
alternative to backing up you could detach the user databases and re-attach
them, once you have re-installed SQL Server and service packed it (this may
be the quickest method) but having a backup on disc and/or tape will give
you a second/third level of recovery.
John
"GaryC" wrote:
> I currently have SQL running on an server that used to be used for call
> center operations. There are many orphaned applications on this server and
> we are planning to back up the server, reinstall a freash copy of 2000 server
> and SQL 2000.
> I have seen there is several ways to migrate data back onto the server,
> detach / attach, restore from back up's, etc...
> Our data center who is responsible for the maintenance of the server uses a
> tool called vertias to back up the SQL databases.
> Can anyone tell me the best method of restoring the system?|||Gary
http://vyaskn.tripod.com/moving_sql_server.htm
"GaryC" <GaryC@.discussions.microsoft.com> wrote in message
news:DDAE0D2D-B700-474B-95A8-4FC1D80FEFF8@.microsoft.com...
>I currently have SQL running on an server that used to be used for call
> center operations. There are many orphaned applications on this server
> and
> we are planning to back up the server, reinstall a freash copy of 2000
> server
> and SQL 2000.
> I have seen there is several ways to migrate data back onto the server,
> detach / attach, restore from back up's, etc...
> Our data center who is responsible for the maintenance of the server uses
> a
> tool called vertias to back up the SQL databases.
> Can anyone tell me the best method of restoring the system?|||Hi John
I have started with a new company and will be working from home. We did a
back up onto a memory stick of QuickBooks and I want to put the data onto my
QuickBooks at home. I have put the memory stick in but can't read any of the
data can you please tell me how I can do this?
Michelle
"John Bell" wrote:
> Hi Gary
> Usually it will depend on how big the databases are as to how you plan this.
> You don't say if you normally back your databases up to disc and then to tape
> or use the plug-ins. You also don't say if you are going to reformat the
> drives or not!
> If you backup to disc then you can use those backups to restore the
> databases, providing the drives have not been reformated! If you don't have
> backups on disc you could backup to a networked machine or possibly a plugged
> in device and then use them to restore from. Restoring from tape will be
> possible, but it will probably take significantly longer. You should also
> verify the backups (tape or disc) before you remove SQL Server. As an
> alternative to backing up you could detach the user databases and re-attach
> them, once you have re-installed SQL Server and service packed it (this may
> be the quickest method) but having a backup on disc and/or tape will give
> you a second/third level of recovery.
> John
> "GaryC" wrote:
> > I currently have SQL running on an server that used to be used for call
> > center operations. There are many orphaned applications on this server and
> > we are planning to back up the server, reinstall a freash copy of 2000 server
> > and SQL 2000.
> >
> > I have seen there is several ways to migrate data back onto the server,
> > detach / attach, restore from back up's, etc...
> >
> > Our data center who is responsible for the maintenance of the server uses a
> > tool called vertias to back up the SQL databases.
> >
> > Can anyone tell me the best method of restoring the system?|||This is probably the wrong newsgroup for help with Quickbooks or memory
stick issues. You may be better off posting to a Windows newsgroup, or even
checking with www.quickbooks.com for appropriate help forums.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Michelle" <Michelle@.discussions.microsoft.com> wrote in message
news:71DF43A3-8590-4466-9E6D-5B8052ACB8B4@.microsoft.com...
> Hi John
> I have started with a new company and will be working from home. We did a
> back up onto a memory stick of QuickBooks and I want to put the data onto
> my
> QuickBooks at home. I have put the memory stick in but can't read any of
> the
> data can you please tell me how I can do this?
> Michelle
> "John Bell" wrote:
>> Hi Gary
>> Usually it will depend on how big the databases are as to how you plan
>> this.
>> You don't say if you normally back your databases up to disc and then to
>> tape
>> or use the plug-ins. You also don't say if you are going to reformat the
>> drives or not!
>> If you backup to disc then you can use those backups to restore the
>> databases, providing the drives have not been reformated! If you don't
>> have
>> backups on disc you could backup to a networked machine or possibly a
>> plugged
>> in device and then use them to restore from. Restoring from tape will be
>> possible, but it will probably take significantly longer. You should also
>> verify the backups (tape or disc) before you remove SQL Server. As an
>> alternative to backing up you could detach the user databases and
>> re-attach
>> them, once you have re-installed SQL Server and service packed it (this
>> may
>> be the quickest method) but having a backup on disc and/or tape will
>> give
>> you a second/third level of recovery.
>> John
>> "GaryC" wrote:
>> > I currently have SQL running on an server that used to be used for call
>> > center operations. There are many orphaned applications on this server
>> > and
>> > we are planning to back up the server, reinstall a freash copy of 2000
>> > server
>> > and SQL 2000.
>> >
>> > I have seen there is several ways to migrate data back onto the server,
>> > detach / attach, restore from back up's, etc...
>> >
>> > Our data center who is responsible for the maintenance of the server
>> > uses a
>> > tool called vertias to back up the SQL databases.
>> >
>> > Can anyone tell me the best method of restoring the system?|||Hi Michelle
As Arnie has said Quickbooks is not really the forte of the people answering
the questions in these groups, but there may be some things you can try, such
as being able to browse the files on the memory stick with windows explorer.
If this is not possible or if you can see the device and not the files then
there is something wrong with either the device or the method you are using
to copy the files.
If you can see the files you require then you may want to copy them into a
directory on the PC. If the files have to be in a specific directory you may
have to move them there. Finding out what files are currently present in
Quickbooks may help you determine this. I would also backup the PC and the
existing Quickbooks setup before you start to do anything. You may want to
try using Quickbooks to create a new set of files and see what files change.
This may give you some indication of what files are needed.
I don't know if Quickbooks has a open file type of functionality or an
import facility, if it does then read up on these in the manual as it may
help.
HTH
John
"Michelle" wrote:
> Hi John
> I have started with a new company and will be working from home. We did a
> back up onto a memory stick of QuickBooks and I want to put the data onto my
> QuickBooks at home. I have put the memory stick in but can't read any of the
> data can you please tell me how I can do this?
> Michelle
> "John Bell" wrote:
> > Hi Gary
> >
> > Usually it will depend on how big the databases are as to how you plan this.
> > You don't say if you normally back your databases up to disc and then to tape
> > or use the plug-ins. You also don't say if you are going to reformat the
> > drives or not!
> >
> > If you backup to disc then you can use those backups to restore the
> > databases, providing the drives have not been reformated! If you don't have
> > backups on disc you could backup to a networked machine or possibly a plugged
> > in device and then use them to restore from. Restoring from tape will be
> > possible, but it will probably take significantly longer. You should also
> > verify the backups (tape or disc) before you remove SQL Server. As an
> > alternative to backing up you could detach the user databases and re-attach
> > them, once you have re-installed SQL Server and service packed it (this may
> > be the quickest method) but having a backup on disc and/or tape will give
> > you a second/third level of recovery.
> >
> > John
> >
> > "GaryC" wrote:
> >
> > > I currently have SQL running on an server that used to be used for call
> > > center operations. There are many orphaned applications on this server and
> > > we are planning to back up the server, reinstall a freash copy of 2000 server
> > > and SQL 2000.
> > >
> > > I have seen there is several ways to migrate data back onto the server,
> > > detach / attach, restore from back up's, etc...
> > >
> > > Our data center who is responsible for the maintenance of the server uses a
> > > tool called vertias to back up the SQL databases.
> > >
> > > Can anyone tell me the best method of restoring the system?

Migrating to a new server

I currently have SQL running on an server that used to be used for call
center operations. There are many orphaned applications on this server and
we are planning to back up the server, reinstall a freash copy of 2000 serve
r
and SQL 2000.
I have seen there is several ways to migrate data back onto the server,
detach / attach, restore from back up's, etc...
Our data center who is responsible for the maintenance of the server uses a
tool called vertias to back up the SQL databases.
Can anyone tell me the best method of restoring the system?Hi Gary
Usually it will depend on how big the databases are as to how you plan this.
You don't say if you normally back your databases up to disc and then to tap
e
or use the plug-ins. You also don't say if you are going to reformat the
drives or not!
If you backup to disc then you can use those backups to restore the
databases, providing the drives have not been reformated! If you don't have
backups on disc you could backup to a networked machine or possibly a plugge
d
in device and then use them to restore from. Restoring from tape will be
possible, but it will probably take significantly longer. You should also
verify the backups (tape or disc) before you remove SQL Server. As an
alternative to backing up you could detach the user databases and re-attach
them, once you have re-installed SQL Server and service packed it (this may
be the quickest method) but having a backup on disc and/or tape will give
you a second/third level of recovery.
John
"GaryC" wrote:

> I currently have SQL running on an server that used to be used for call
> center operations. There are many orphaned applications on this server an
d
> we are planning to back up the server, reinstall a freash copy of 2000 ser
ver
> and SQL 2000.
> I have seen there is several ways to migrate data back onto the server,
> detach / attach, restore from back up's, etc...
> Our data center who is responsible for the maintenance of the server uses
a
> tool called vertias to back up the SQL databases.
> Can anyone tell me the best method of restoring the system?|||Gary
http://vyaskn.tripod.com/moving_sql_server.htm
"GaryC" <GaryC@.discussions.microsoft.com> wrote in message
news:DDAE0D2D-B700-474B-95A8-4FC1D80FEFF8@.microsoft.com...
>I currently have SQL running on an server that used to be used for call
> center operations. There are many orphaned applications on this server
> and
> we are planning to back up the server, reinstall a freash copy of 2000
> server
> and SQL 2000.
> I have seen there is several ways to migrate data back onto the server,
> detach / attach, restore from back up's, etc...
> Our data center who is responsible for the maintenance of the server uses
> a
> tool called vertias to back up the SQL databases.
> Can anyone tell me the best method of restoring the system?|||Hi John
I have started with a new company and will be working from home. We did a
back up onto a memory stick of QuickBooks and I want to put the data onto my
QuickBooks at home. I have put the memory stick in but can't read any of th
e
data can you please tell me how I can do this?
Michelle
"John Bell" wrote:
[vbcol=seagreen]
> Hi Gary
> Usually it will depend on how big the databases are as to how you plan thi
s.
> You don't say if you normally back your databases up to disc and then to t
ape
> or use the plug-ins. You also don't say if you are going to reformat the
> drives or not!
> If you backup to disc then you can use those backups to restore the
> databases, providing the drives have not been reformated! If you don't hav
e
> backups on disc you could backup to a networked machine or possibly a plug
ged
> in device and then use them to restore from. Restoring from tape will be
> possible, but it will probably take significantly longer. You should also
> verify the backups (tape or disc) before you remove SQL Server. As an
> alternative to backing up you could detach the user databases and re-attac
h
> them, once you have re-installed SQL Server and service packed it (this ma
y
> be the quickest method) but having a backup on disc and/or tape will give
> you a second/third level of recovery.
> John
> "GaryC" wrote:
>|||This is probably the wrong newsgroup for help with Quickbooks or memory
stick issues. You may be better off posting to a Windows newsgroup, or even
checking with www.quickbooks.com for appropriate help forums.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Michelle" <Michelle@.discussions.microsoft.com> wrote in message
news:71DF43A3-8590-4466-9E6D-5B8052ACB8B4@.microsoft.com...[vbcol=seagreen]
> Hi John
> I have started with a new company and will be working from home. We did a
> back up onto a memory stick of QuickBooks and I want to put the data onto
> my
> QuickBooks at home. I have put the memory stick in but can't read any of
> the
> data can you please tell me how I can do this?
> Michelle
> "John Bell" wrote:
>|||Hi Michelle
As Arnie has said Quickbooks is not really the forte of the people answering
the questions in these groups, but there may be some things you can try, suc
h
as being able to browse the files on the memory stick with windows explorer.
If this is not possible or if you can see the device and not the files then
there is something wrong with either the device or the method you are using
to copy the files.
If you can see the files you require then you may want to copy them into a
directory on the PC. If the files have to be in a specific directory you may
have to move them there. Finding out what files are currently present in
Quickbooks may help you determine this. I would also backup the PC and the
existing Quickbooks setup before you start to do anything. You may want to
try using Quickbooks to create a new set of files and see what files change.
This may give you some indication of what files are needed.
I don't know if Quickbooks has a open file type of functionality or an
import facility, if it does then read up on these in the manual as it may
help.
HTH
John
"Michelle" wrote:
[vbcol=seagreen]
> Hi John
> I have started with a new company and will be working from home. We did a
> back up onto a memory stick of QuickBooks and I want to put the data onto
my
> QuickBooks at home. I have put the memory stick in but can't read any of
the
> data can you please tell me how I can do this?
> Michelle
> "John Bell" wrote:
>