Haslett, Andrew
andrew.haslett at ilc.gov.au
Mon Aug 28 02:15:09 CDT 2006
Turn *off* simple file sharing. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Monday, 28 August 2006 11:07 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database toanotherSQLServer >If space on the stick or CD or DVD is really a problem, you could skip >or truncate the Log file. LOL, I have three files. One is 150 GIG, the other two are 140 GIG but only 56 GIG actually used. Unlikely to fit on a memory stick, or a dvd - even zipped. But if I can detach them, then just move the entire disks and then reattach that would be fine. I really need to get these disks moved to the new machine anyway. Which leaves me with the issue of why EM is not able to attach to the database on the other machine. This was working in the past. These are simple Windows XP Pro boxes, identical username / password on all the boxes. Workgroup, no domains. Simple file sharing is working, I can see directories on the other boxes. Each machine has a SQL Server running. Each machine can see its own local database, and I can see the other machine (it comes up in a list of machines / databases to connect to) but the connect itself fails with a "can't use guest". All of them are set up to use Windows Server authentication. Why is it trying to use Guest as opposed to using the current logged in user on the current machine (jwcolby)? John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Sunday, August 27, 2006 4:45 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQLServer In that case, the simplest means is detach the db, copy it to a memory stick or something, then copy it to the data directory of the new machine, and finally attach it. This sidesteps the problem of why you cannot see each box from the other, but one thing at a time. Presumably the most important thing is to get the db there. Depending on the size of the MDF and LDF files, you may need to ZIP or RAR them first, then extract them upon arrival. If space on the stick or CD or DVD is really a problem, you could skip or truncate the Log file. hth. Arthur ----- Original Message ---- From: JWColby <jwcolby at colbyconsulting.com> To: dba-sqlserver at databaseadvisors.com Sent: Sunday, August 27, 2006 1:26:31 PM Subject: Re: [dba-SQLServer] [AccessD] Transferring a database to anotherSQL Server SQL Server 2K John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ *** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not.