moving all databases to new server including sql server configurat

Hi,
We are getting a new server and need to move all the sql server database to this new server including configuration of the current sql server software. What is the best way to do this? Currently, we do not have any backup of the production.
Thanks,
Jack
Probably the easiest way is to detach the databases and copy to new server and attach. Depending on your security model, you could also use the DTS import login functions to bring users over
"Jack" wrote:

> Hi,
> We are getting a new server and need to move all the sql server database to this new server including configuration of the current sql server software. What is the best way to do this? Currently, we do not have any backup of the production.
> Thanks,
> Jack
|||Have a look at this: http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:B4462402-6091-4D5B-B0DB-1C61BE5F3E45@.microsoft.com...
Hi,
We are getting a new server and need to move all the sql server database to
this new server including configuration of the current sql server software.
What is the best way to do this? Currently, we do not have any backup of the
production.
Thanks,
Jack
|||Hi,
Have a look into the below link for moving all the databases to new server.
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Thanks
Hari
MCDBA
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:B4462402-6091-4D5B-B0DB-1C61BE5F3E45@.microsoft.com...
> Hi,
> We are getting a new server and need to move all the sql server database
to this new server including configuration of the current sql server
software. What is the best way to do this? Currently, we do not have any
backup of the production.
> Thanks,
> Jack

moving all databases to new server including sql server configurat

Hi,
We are getting a new server and need to move all the sql server database to
this new server including configuration of the current sql server software.
What is the best way to do this? Currently, we do not have any backup of the
production.
Thanks,
JackProbably the easiest way is to detach the databases and copy to new server a
nd attach. Depending on your security model, you could also use the DTS imp
ort login functions to bring users over
"Jack" wrote:

> Hi,
> We are getting a new server and need to move all the sql server database t
o this new server including configuration of the current sql server software
. What is the best way to do this? Currently, we do not have any backup of t
he production.
> Thanks,
> Jack|||Have a look at this: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:B4462402-6091-4D5B-B0DB-1C61BE5F3E45@.microsoft.com...
Hi,
We are getting a new server and need to move all the sql server database to
this new server including configuration of the current sql server software.
What is the best way to do this? Currently, we do not have any backup of the
production.
Thanks,
Jack|||Hi,
Have a look into the below link for moving all the databases to new server.
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Thanks
Hari
MCDBA
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:B4462402-6091-4D5B-B0DB-1C61BE5F3E45@.microsoft.com...
> Hi,
> We are getting a new server and need to move all the sql server database
to this new server including configuration of the current sql server
software. What is the best way to do this? Currently, we do not have any
backup of the production.
> Thanks,
> Jack

Move Temp DB and Logs to get more speed?

We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!It's a best practice to have the data and logs on separate partitions. This
is both for safety (High Availability) as well as performance. Also, try to
keep tempdb separate from your app DB's. Thus, you could go with:
D: app data
F: app log
G: tempdb
Try that first. You can also move the tempdb log to F: and see if that
improves or degrades performance. Logs should not be placed on RAID5
partitions.
HTH
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!|||Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Initially, try both data and log for tempdb. If that is satisfactory, you
can leave it. If you still have perf issues, then move the log to another
drive.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>|||Great news. Thanx for the follow-up. :-)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:uDeCmGTiIHA.1164@.TK2MSFTNGP02.phx.gbl...
Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>

Move databas from express to sql 2000

Hi!

I have created i webpage whos has a logged in system which is cretead in VS 2005 with the function ASP.NET configuration.

And know will i move all databas to i a MSSQL 2000 there i only can have one databas, And know i have ASP.NET logged in Databas and one site databas.

I just wondering if its possible to make i virtual connection with MSSQL 2000? If not somebody has some idés for me?

I hope you can understand me.

If I understand, right now on your development environment you have the ASPNETDB database (logged in system) and also a site database. And you need to move to SQL Server 2000 where you'll only have one database.

You can combine the security schema (aspnetdb) and the site schema into the same SQL 2000 database - this should not be a problem. To install the ASP.Net security schema into an existing SQL 2000 database, you can run aspnet_regsql.exe against the database. So if the site database is already on this SQL 2000, just run aspnet_regsql against the same database (or get the DBA to do so) and then you'll need to point your database connection (in the web.config) against the SQL Server.

|||

Ok, tanks!

But i don't know how i do that. can you explain? If you want step by step.

The sql server and the webserver is on a webhotel, so i can't do any configuration.

|||

someone who can explain for me?

Now i just have to move the login database (ASTNETDB) into another database (a SQL 2000 database)

Someone?

|||

So now i know how i have to do. But when i use the aspnet_regsql.exe so i get a error.

Error

Grantor does not have GRANT permission.

The error comes when installCommon.sql