Hi,
The Windows 2000 Server (that has MSSQL Server installed) is corrupted.
Can anybody tell me how I can make the existing SQL data files work in
another Windows 2000 Server?
What should I do?
Thanks & Regards,
KS
Hi KS !
You've got the data and log file ?
I've got the german EM, so don't know the exact names
of the menu items in english version of EM, but i'll try.
On your new SQL-Server EM:
Right-Click on Databases -> All Tasks -> Attach DB
then choose your mdf-file, and that's it. (Hope so!)
Hope these instructions help.
Let me know about it.
Best regards,
|||Smuddi wrote:
> Hi KS !
> You've got the data and log file ?
> I've got the german EM, so don't know the exact names
> of the menu items in english version of EM, but i'll try.
> On your new SQL-Server EM:
> Right-Click on Databases -> All Tasks -> Attach DB
> then choose your mdf-file, and that's it. (Hope so!)
> Hope these instructions help.
> Let me know about it.
> Best regards,
hi,
That's ok but you'll still have orfan users. Drop and create database users
again!
regards,
Zarko
|||Hello KS
Assuming you have all database files (including system databases - master,
msdb), you should follow the steps below :
1. Install SQL Server to the same location on the second server (as your
old server)
2. Apply the same service pack and/or hotfix that you had on your old
server.
3. Stop SQL Server services and replace all database files with the ones
that you had from your old server.
Remember the above step may not work correctly if you do not have the
system database file level backups. If this condition was a result of file
system corruption and the database files were copied after the corruption,
its possible that they may be corrupted too. So the above steps may not
work.
If you only have the user database files, follow the step in the article
below :
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
There is also a section in the above article regarding recovering orphaned
logins.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Showing posts with label existing. Show all posts
Showing posts with label existing. Show all posts
Saturday, February 25, 2012
MSSQL Server Recovery
Hi,
The Windows 2000 Server (that has MSSQL Server installed) is corrupted.
Can anybody tell me how I can make the existing SQL data files work in
another Windows 2000 Server?
What should I do?
Thanks & Regards,
KSHi KS !
You've got the data and log file ?
I've got the german EM, so don't know the exact names
of the menu items in english version of EM, but i'll try.
On your new SQL-Server EM:
Right-Click on Databases -> All Tasks -> Attach DB
then choose your mdf-file, and that's it. (Hope so!)
Hope these instructions help.
Let me know about it.
Best regards,|||Smuddi wrote:
> Hi KS !
> You've got the data and log file ?
> I've got the german EM, so don't know the exact names
> of the menu items in english version of EM, but i'll try.
> On your new SQL-Server EM:
> Right-Click on Databases -> All Tasks -> Attach DB
> then choose your mdf-file, and that's it. (Hope so!)
> Hope these instructions help.
> Let me know about it.
> Best regards,
hi,
That's ok but you'll still have orfan users. Drop and create database users
again!
regards,
Zarko|||Hello KS
Assuming you have all database files (including system databases - master,
msdb), you should follow the steps below :
1. Install SQL Server to the same location on the second server (as your
old server)
2. Apply the same service pack and/or hotfix that you had on your old
server.
3. Stop SQL Server services and replace all database files with the ones
that you had from your old server.
Remember the above step may not work correctly if you do not have the
system database file level backups. If this condition was a result of file
system corruption and the database files were copied after the corruption,
its possible that they may be corrupted too. So the above steps may not
work.
If you only have the user database files, follow the step in the article
below :
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
There is also a section in the above article regarding recovering orphaned
logins.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
The Windows 2000 Server (that has MSSQL Server installed) is corrupted.
Can anybody tell me how I can make the existing SQL data files work in
another Windows 2000 Server?
What should I do?
Thanks & Regards,
KSHi KS !
You've got the data and log file ?
I've got the german EM, so don't know the exact names
of the menu items in english version of EM, but i'll try.
On your new SQL-Server EM:
Right-Click on Databases -> All Tasks -> Attach DB
then choose your mdf-file, and that's it. (Hope so!)
Hope these instructions help.
Let me know about it.
Best regards,|||Smuddi wrote:
> Hi KS !
> You've got the data and log file ?
> I've got the german EM, so don't know the exact names
> of the menu items in english version of EM, but i'll try.
> On your new SQL-Server EM:
> Right-Click on Databases -> All Tasks -> Attach DB
> then choose your mdf-file, and that's it. (Hope so!)
> Hope these instructions help.
> Let me know about it.
> Best regards,
hi,
That's ok but you'll still have orfan users. Drop and create database users
again!
regards,
Zarko|||Hello KS
Assuming you have all database files (including system databases - master,
msdb), you should follow the steps below :
1. Install SQL Server to the same location on the second server (as your
old server)
2. Apply the same service pack and/or hotfix that you had on your old
server.
3. Stop SQL Server services and replace all database files with the ones
that you had from your old server.
Remember the above step may not work correctly if you do not have the
system database file level backups. If this condition was a result of file
system corruption and the database files were copied after the corruption,
its possible that they may be corrupted too. So the above steps may not
work.
If you only have the user database files, follow the step in the article
below :
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
There is also a section in the above article regarding recovering orphaned
logins.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
MSSQL Server Recovery
Hi,
The Windows 2000 Server (that has MSSQL Server installed) is corrupted.
Can anybody tell me how I can make the existing SQL data files work in
another Windows 2000 Server?
What should I do?
Thanks & Regards,
KSHi KS !
You've got the data and log file ?
I've got the german EM, so don't know the exact names
of the menu items in english version of EM, but i'll try.
On your new SQL-Server EM:
Right-Click on Databases -> All Tasks -> Attach DB
then choose your mdf-file, and that's it. (Hope so!)
Hope these instructions help.
Let me know about it.
Best regards,|||Can you give us some indication on the status of your
server i.e. is it accessable.
Can you also give us some indication of your backups and
any replication.
Peter
"It's true hard work never killed anybody, but I figure,
why take the chance?"
Ronald Reagan
>--Original Message--
>Hi,
>The Windows 2000 Server (that has MSSQL Server
installed) is corrupted.
>Can anybody tell me how I can make the existing SQL data
files work in
>another Windows 2000 Server?
>What should I do?
>Thanks & Regards,
>KS
>
>.
>|||Smuddi wrote:
> Hi KS !
> You've got the data and log file ?
> I've got the german EM, so don't know the exact names
> of the menu items in english version of EM, but i'll try.
> On your new SQL-Server EM:
> Right-Click on Databases -> All Tasks -> Attach DB
> then choose your mdf-file, and that's it. (Hope so!)
> Hope these instructions help.
> Let me know about it.
> Best regards,
hi,
That's ok but you'll still have orfan users. Drop and create database users
again!
regards,
Zarko|||Hello KS
Assuming you have all database files (including system databases - master,
msdb), you should follow the steps below :
1. Install SQL Server to the same location on the second server (as your
old server)
2. Apply the same service pack and/or hotfix that you had on your old
server.
3. Stop SQL Server services and replace all database files with the ones
that you had from your old server.
Remember the above step may not work correctly if you do not have the
system database file level backups. If this condition was a result of file
system corruption and the database files were copied after the corruption,
its possible that they may be corrupted too. So the above steps may not
work.
If you only have the user database files, follow the step in the article
below :
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
There is also a section in the above article regarding recovering orphaned
logins.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi,
Due to I cannot log into Windows 2000 Server (installed by
ex-administrator),
I need to install a new Windows 2000 Server.
And transfer the existing data files to the new machine.
Regards,
KS
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:136701c48c22$49618100$a501280a@.phx.gbl...
> Can you give us some indication on the status of your
> server i.e. is it accessable.
> Can you also give us some indication of your backups and
> any replication.
> Peter
> "It's true hard work never killed anybody, but I figure,
> why take the chance?"
> Ronald Reagan
>
> >--Original Message--
> >Hi,
> >
> >The Windows 2000 Server (that has MSSQL Server
> installed) is corrupted.
> >
> >Can anybody tell me how I can make the existing SQL data
> files work in
> >another Windows 2000 Server?
> >
> >What should I do?
> >
> >Thanks & Regards,
> >KS
> >
> >
> >.
> >
The Windows 2000 Server (that has MSSQL Server installed) is corrupted.
Can anybody tell me how I can make the existing SQL data files work in
another Windows 2000 Server?
What should I do?
Thanks & Regards,
KSHi KS !
You've got the data and log file ?
I've got the german EM, so don't know the exact names
of the menu items in english version of EM, but i'll try.
On your new SQL-Server EM:
Right-Click on Databases -> All Tasks -> Attach DB
then choose your mdf-file, and that's it. (Hope so!)
Hope these instructions help.
Let me know about it.
Best regards,|||Can you give us some indication on the status of your
server i.e. is it accessable.
Can you also give us some indication of your backups and
any replication.
Peter
"It's true hard work never killed anybody, but I figure,
why take the chance?"
Ronald Reagan
>--Original Message--
>Hi,
>The Windows 2000 Server (that has MSSQL Server
installed) is corrupted.
>Can anybody tell me how I can make the existing SQL data
files work in
>another Windows 2000 Server?
>What should I do?
>Thanks & Regards,
>KS
>
>.
>|||Smuddi wrote:
> Hi KS !
> You've got the data and log file ?
> I've got the german EM, so don't know the exact names
> of the menu items in english version of EM, but i'll try.
> On your new SQL-Server EM:
> Right-Click on Databases -> All Tasks -> Attach DB
> then choose your mdf-file, and that's it. (Hope so!)
> Hope these instructions help.
> Let me know about it.
> Best regards,
hi,
That's ok but you'll still have orfan users. Drop and create database users
again!
regards,
Zarko|||Hello KS
Assuming you have all database files (including system databases - master,
msdb), you should follow the steps below :
1. Install SQL Server to the same location on the second server (as your
old server)
2. Apply the same service pack and/or hotfix that you had on your old
server.
3. Stop SQL Server services and replace all database files with the ones
that you had from your old server.
Remember the above step may not work correctly if you do not have the
system database file level backups. If this condition was a result of file
system corruption and the database files were copied after the corruption,
its possible that they may be corrupted too. So the above steps may not
work.
If you only have the user database files, follow the step in the article
below :
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
There is also a section in the above article regarding recovering orphaned
logins.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi,
Due to I cannot log into Windows 2000 Server (installed by
ex-administrator),
I need to install a new Windows 2000 Server.
And transfer the existing data files to the new machine.
Regards,
KS
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:136701c48c22$49618100$a501280a@.phx.gbl...
> Can you give us some indication on the status of your
> server i.e. is it accessable.
> Can you also give us some indication of your backups and
> any replication.
> Peter
> "It's true hard work never killed anybody, but I figure,
> why take the chance?"
> Ronald Reagan
>
> >--Original Message--
> >Hi,
> >
> >The Windows 2000 Server (that has MSSQL Server
> installed) is corrupted.
> >
> >Can anybody tell me how I can make the existing SQL data
> files work in
> >another Windows 2000 Server?
> >
> >What should I do?
> >
> >Thanks & Regards,
> >KS
> >
> >
> >.
> >
Monday, February 20, 2012
MSSQL Replication
Our existing SQL Server is experiencing some troubles and we would like to replace it with new hardware. Of course a migration will be in order to move off of this hardware and onto the new.
To better protect our business critical needs we have decided to implement SQL Server Replication. The SQL Server is what helps drive our everyday business. Without it, we are "dead in the water"! The other day, we lost approximately 10 hours of productivity until SQL Services could be restored.
My question is, if it would be wise to have yet a 3rd server used as a Distributor for Replication or if it would be okay to have the Distributor and Publisher on the same server?
I am concerned that there may be performance problems if we place the two roles on the same machine event though the hardware is very good. Below is the important server configuration.
Windows 2003 Standard Edition
SQL Server Standard Edition
Dual 2.4Ghz with HyperThreading
2GB of RAM
RAID5 for MDF Files
RAID1 for LDF Files
Thank you all for your responses and suggestions.It's always recommended by MS to consider having a server per role. In addition you may want to set up Alternate location and file compression, which will lower network activity caused by replication process.|||I found an aritcle that outlines some performance considerations. I think it is exactly what I am looking for.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
To better protect our business critical needs we have decided to implement SQL Server Replication. The SQL Server is what helps drive our everyday business. Without it, we are "dead in the water"! The other day, we lost approximately 10 hours of productivity until SQL Services could be restored.
My question is, if it would be wise to have yet a 3rd server used as a Distributor for Replication or if it would be okay to have the Distributor and Publisher on the same server?
I am concerned that there may be performance problems if we place the two roles on the same machine event though the hardware is very good. Below is the important server configuration.
Windows 2003 Standard Edition
SQL Server Standard Edition
Dual 2.4Ghz with HyperThreading
2GB of RAM
RAID5 for MDF Files
RAID1 for LDF Files
Thank you all for your responses and suggestions.It's always recommended by MS to consider having a server per role. In addition you may want to set up Alternate location and file compression, which will lower network activity caused by replication process.|||I found an aritcle that outlines some performance considerations. I think it is exactly what I am looking for.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
Subscribe to:
Posts (Atom)