database problem: windows

Showing posts with label windows. Show all posts

Friday, March 30, 2012

Restrict users to modify tabble structure

Is it possible to restrict users to modify the table structure. Most of our
users are using "Windows authentication"
Thanks for any help.
J Justin
You need to limit what permissions each user has. Modify the security =
on each group or individual so that they have only the rights that they =
need. If you want to limit what they can do you will want to clear all =
checkboxes on the "server roles" tab and you will want to make sure that =
they have the appropriate database roles assigned. You access the forms =
that I am talking about via Enterprise Manager. Drill into the security =
folder, Logins node. double-click on a specific login to view its =
properties.
--=20
Keith
"Justin" <justinkumar@.hotmail.com> wrote in message =
news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> Is it possible to restrict users to modify the table structure. Most =
of our
> users are using "Windows authentication"
> Thanks for any help.
>=20
> J Justin
>=20
>
|||Just make sure that they don't have such permissions/privileges in your database. I.e., should not have the
sysadmin server role. Should not be dbo in the database. Should not have db_ddladmin or db_owner database
role.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Justin" <justinkumar@.hotmail.com> wrote in message news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> Is it possible to restrict users to modify the table structure. Most of our
> users are using "Windows authentication"
> Thanks for any help.
> J Justin
>

Restrict users to modify tabble structure

Is it possible to restrict users to modify the table structure. Most of our
users are using "Windows authentication"
Thanks for any help.
J JustinYou need to limit what permissions each user has. Modify the security =
on each group or individual so that they have only the rights that they =
need. If you want to limit what they can do you will want to clear all =
checkboxes on the "server roles" tab and you will want to make sure that =
they have the appropriate database roles assigned. You access the forms =
that I am talking about via Enterprise Manager. Drill into the security =
folder, Logins node. double-click on a specific login to view its =
properties.
--=20
Keith
"Justin" <justinkumar@.hotmail.com> wrote in message =
news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> Is it possible to restrict users to modify the table structure. Most =
of our
> users are using "Windows authentication"
> Thanks for any help.
>=20
> J Justin
>=20
>|||Just make sure that they don't have such permissions/privileges in your data
base. I.e., should not have the
sysadmin server role. Should not be dbo in the database. Should not have db_
ddladmin or db_owner database
role.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Justin" <justinkumar@.hotmail.com> wrote in message news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx
.gbl...
> Is it possible to restrict users to modify the table structure. Most of ou
r
> users are using "Windows authentication"
> Thanks for any help.
> J Justin
>

Restrict users to modify tabble structure

Is it possible to restrict users to modify the table structure. Most of our
users are using "Windows authentication"
Thanks for any help.
J JustinYou need to limit what permissions each user has. Modify the security =on each group or individual so that they have only the rights that they =need. If you want to limit what they can do you will want to clear all =checkboxes on the "server roles" tab and you will want to make sure that =they have the appropriate database roles assigned. You access the forms =that I am talking about via Enterprise Manager. Drill into the security =folder, Logins node. double-click on a specific login to view its =properties.
-- Keith
"Justin" <justinkumar@.hotmail.com> wrote in message =news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> Is it possible to restrict users to modify the table structure. Most =of our
> users are using "Windows authentication"
> Thanks for any help.
> > J Justin
> >|||Just make sure that they don't have such permissions/privileges in your database. I.e., should not have the
sysadmin server role. Should not be dbo in the database. Should not have db_ddladmin or db_owner database
role.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Justin" <justinkumar@.hotmail.com> wrote in message news:%23nTbnRiTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> Is it possible to restrict users to modify the table structure. Most of our
> users are using "Windows authentication"
> Thanks for any help.
> J Justin
>sql

Monday, March 26, 2012

Restoring the master to different drive letters

Can you restore the master database, running on windows server 2000, sql
server 2000 from a backup that was taken from c:\ to another server
restoring to d:\?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Hi

See:
http://support.microsoft.com/defaul...ben-us%3b224071

John

"spec_server" <spec_9@.nwy.com> wrote in message
news:415c6810$0$26132$c397aba@.news.newsgroups.ws.. .
> Can you restore the master database, running on windows server 2000, sql
> server 2000 from a backup that was taken from c:\ to another server
> restoring to d:\?
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Wednesday, March 21, 2012

restoring SQL 2000 on Windows 2000

i am trying to restore sql 2000 on Windows 2000 from a
tape backup created thru Veritas 8.6. The restore
completes successfully and everything seems fine except
for the fact that the sql service fails to start and when
i try to start sql, it returns the error message "the path
was not found"I'm guessing that one of your parameters in the registry point to some
location different then where you restored the files. Review the registry
entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLSever\Parameters
Make sure all the parmeters poin to valid files, the ones you restore.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"malejandro" <malejandrdo@.armadillohomes.com> wrote in message
news:12d0401c44349$e884d6f0$a601280a@.phx
.gbl...
> i am trying to restore sql 2000 on Windows 2000 from a
> tape backup created thru Veritas 8.6. The restore
> completes successfully and everything seems fine except
> for the fact that the sql service fails to start and when
> i try to start sql, it returns the error message "the path
> was not found"

restoring SQL 2000 on Windows 2000

i am trying to restore sql 2000 on windows 2000 from a
tape backup created thru Veritas 8.6. The restore
completes successfully and everything seems fine except
for the fact that the sql service fails to start and when
i try to start sql, it returns the error message "the path
was not found"I'm guessing that one of your parameters in the registry point to some
location different then where you restored the files. Review the registry
entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLSever\Parameters
Make sure all the parmeters poin to valid files, the ones you restore.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"malejandro" <malejandrdo@.armadillohomes.com> wrote in message
news:12d0401c44349$e884d6f0$a601280a@.phx.gbl...
> i am trying to restore sql 2000 on windows 2000 from a
> tape backup created thru Veritas 8.6. The restore
> completes successfully and everything seems fine except
> for the fact that the sql service fails to start and when
> i try to start sql, it returns the error message "the path
> was not found"

restoring SQL 2000 on Windows 2000

i am trying to restore sql 2000 on windows 2000 from a
tape backup created thru Veritas 8.6. The restore
completes successfully and everything seems fine except
for the fact that the sql service fails to start and when
i try to start sql, it returns the error message "the path
was not found"
I'm guessing that one of your parameters in the registry point to some
location different then where you restored the files. Review the registry
entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLSever\P arameters
Make sure all the parmeters poin to valid files, the ones you restore.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"malejandro" <malejandrdo@.armadillohomes.com> wrote in message
news:12d0401c44349$e884d6f0$a601280a@.phx.gbl...
> i am trying to restore sql 2000 on windows 2000 from a
> tape backup created thru Veritas 8.6. The restore
> completes successfully and everything seems fine except
> for the fact that the sql service fails to start and when
> i try to start sql, it returns the error message "the path
> was not found"
sql

Monday, March 12, 2012

Restoring Master database

Hi,
Production Server: Windows 2000 server, SQL Server 2000 SP2
Test Server: Windows 2003 server, SQL Server 2000 SP3
I have to restore the master database from Production Server to Test Server.
Would it cause any issues? Thanks.Sharman,
Yes. Since logins, databases, linked servers, etc. are all defined in
master, those definitions on the Test Server will be replaced with the
definitions from the Production Server. Any unique logins will be
eliminated, databases may become unattached, and so forth.
So, you can do it, but you have to be very careful not to lose anything that
you need. You might restore master to your test server as
'master_from_prod' and determine what you have to do to merge any
differences.
(I do not fathom why Production master is needed on Test unless a pretty
good slice of other databases is also being brought over to Test as well.)
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:985B0C8F-6D5E-481C-8FD4-A60B7F043FB0@.microsoft.com...
> Hi,
> Production Server: Windows 2000 server, SQL Server 2000 SP2
> Test Server: Windows 2003 server, SQL Server 2000 SP3
> I have to restore the master database from Production Server to Test
> Server.
> Would it cause any issues? Thanks.|||I am asking this question because of the different Service Packs on
Production and Test servers with Production having a lower Service Pack. I
have read that Service Packs apply changes to system tables and I am
restoring a master created on SP2 on a SQL Server running SP3.
Once the restore of master is successful I will be restoring the other
system and user databases from Production Server as well.
"Russell Fields" wrote:
> Sharman,
> Yes. Since logins, databases, linked servers, etc. are all defined in
> master, those definitions on the Test Server will be replaced with the
> definitions from the Production Server. Any unique logins will be
> eliminated, databases may become unattached, and so forth.
> So, you can do it, but you have to be very careful not to lose anything that
> you need. You might restore master to your test server as
> 'master_from_prod' and determine what you have to do to merge any
> differences.
> (I do not fathom why Production master is needed on Test unless a pretty
> good slice of other databases is also being brought over to Test as well.)
> RLF
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:985B0C8F-6D5E-481C-8FD4-A60B7F043FB0@.microsoft.com...
> > Hi,
> >
> > Production Server: Windows 2000 server, SQL Server 2000 SP2
> > Test Server: Windows 2003 server, SQL Server 2000 SP3
> >
> > I have to restore the master database from Production Server to Test
> > Server.
> > Would it cause any issues? Thanks.
>
>|||sharman,
It was a while back, but I believe that SQL 2000 SP4 was the only one that
changed the format of the system tables in the SQL 2000 timeline.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:4BB1EF1C-D7B9-43F6-B4AB-A64CA0A20834@.microsoft.com...
>I am asking this question because of the different Service Packs on
> Production and Test servers with Production having a lower Service Pack. I
> have read that Service Packs apply changes to system tables and I am
> restoring a master created on SP2 on a SQL Server running SP3.
> Once the restore of master is successful I will be restoring the other
> system and user databases from Production Server as well.
>
> "Russell Fields" wrote:
>> Sharman,
>> Yes. Since logins, databases, linked servers, etc. are all defined in
>> master, those definitions on the Test Server will be replaced with the
>> definitions from the Production Server. Any unique logins will be
>> eliminated, databases may become unattached, and so forth.
>> So, you can do it, but you have to be very careful not to lose anything
>> that
>> you need. You might restore master to your test server as
>> 'master_from_prod' and determine what you have to do to merge any
>> differences.
>> (I do not fathom why Production master is needed on Test unless a pretty
>> good slice of other databases is also being brought over to Test as
>> well.)
>> RLF
>> "sharman" <sharman@.discussions.microsoft.com> wrote in message
>> news:985B0C8F-6D5E-481C-8FD4-A60B7F043FB0@.microsoft.com...
>> > Hi,
>> >
>> > Production Server: Windows 2000 server, SQL Server 2000 SP2
>> > Test Server: Windows 2003 server, SQL Server 2000 SP3
>> >
>> > I have to restore the master database from Production Server to Test
>> > Server.
>> > Would it cause any issues? Thanks.
>>|||There is more to it than logins I think. Isn't the location of all
databases stored there? Other stuff too . . .
--
TheSQLGuru
President
Indicium Resources, Inc.
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:e$$AvFNuHHA.3404@.TK2MSFTNGP03.phx.gbl...
> Sharman,
> Yes. Since logins, databases, linked servers, etc. are all defined in
> master, those definitions on the Test Server will be replaced with the
> definitions from the Production Server. Any unique logins will be
> eliminated, databases may become unattached, and so forth.
> So, you can do it, but you have to be very careful not to lose anything
> that you need. You might restore master to your test server as
> 'master_from_prod' and determine what you have to do to merge any
> differences.
> (I do not fathom why Production master is needed on Test unless a pretty
> good slice of other databases is also being brought over to Test as well.)
> RLF
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:985B0C8F-6D5E-481C-8FD4-A60B7F043FB0@.microsoft.com...
>> Hi,
>> Production Server: Windows 2000 server, SQL Server 2000 SP2
>> Test Server: Windows 2003 server, SQL Server 2000 SP3
>> I have to restore the master database from Production Server to Test
>> Server.
>> Would it cause any issues? Thanks.
>|||I'd rather apply the SQL patches than restore master from PROD to TEST
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:utqOUsZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> There is more to it than logins I think. Isn't the location of all
> databases stored there? Other stuff too . . .
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:e$$AvFNuHHA.3404@.TK2MSFTNGP03.phx.gbl...
>> Sharman,
>> Yes. Since logins, databases, linked servers, etc. are all defined in
>> master, those definitions on the Test Server will be replaced with the
>> definitions from the Production Server. Any unique logins will be
>> eliminated, databases may become unattached, and so forth.
>> So, you can do it, but you have to be very careful not to lose anything
>> that you need. You might restore master to your test server as
>> 'master_from_prod' and determine what you have to do to merge any
>> differences.
>> (I do not fathom why Production master is needed on Test unless a pretty
>> good slice of other databases is also being brought over to Test as
>> well.)
>> RLF
>> "sharman" <sharman@.discussions.microsoft.com> wrote in message
>> news:985B0C8F-6D5E-481C-8FD4-A60B7F043FB0@.microsoft.com...
>> Hi,
>> Production Server: Windows 2000 server, SQL Server 2000 SP2
>> Test Server: Windows 2003 server, SQL Server 2000 SP3
>> I have to restore the master database from Production Server to Test
>> Server.
>> Would it cause any issues? Thanks.
>>
>

Restoring Master database

Restoring master and msdb on a different server

Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
Many thanks,
OskarCan you do it? Sure. Is it a good idea or not? That depends on why you
would want to do it. What are you trying to accomplish?
Also, the weaker machine, you said, is only a 2-way CPU box, why would you
have a 2 CPU affinity set on it?
Sincerely,
Anthony Thomas
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
Many thanks,
Oskar|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manne
r.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and i
t
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>

Restoring master and msdb on a different server

Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
Many thanks,
Oskar
Can you do it? Sure. Is it a good idea or not? That depends on why you
would want to do it. What are you trying to accomplish?
Also, the weaker machine, you said, is only a 2-way CPU box, why would you
have a 2 CPU affinity set on it?
Sincerely,
Anthony Thomas

"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
Many thanks,
Oskar
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>
|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
Many thanks,
Oskar
"Anthony Thomas" wrote:

> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>

Friday, March 9, 2012

Restoring master and msdb on a different server

Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
--
Many thanks,
OskarCan you do it? Sure. Is it a good idea or not? That depends on why you
would want to do it. What are you trying to accomplish?
Also, the weaker machine, you said, is only a 2-way CPU box, why would you
have a 2 CPU affinity set on it?
Sincerely,
Anthony Thomas
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
Hi
I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
Server 2003 SP1 and MS SQL Server 2000 SP3.
The SQL Server on the weaker machine has affinity mask turned on to use
only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
located on drive E:.
The SQL Server on the stronger machine has master and msdb located on
drive C:, affinity mask set off, and dynamic memory allocation set on.
Can I restore the master database from the weaker machine on the stronger
machine and is it a good idea?
--
Many thanks,
Oskar|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>|||I was hoping that this would be an easier way to migrate the SQL Server
information (e.g. logins, jobs etc.) from the weaker server to the stronger
one. But then when I started to think of moving the data files of master and
msdb databases, I wasn't sure if I that would be possible in the usual manner.
I have the affinity set on the weaker server so that only one logical CPU on
each of the physical Xeon CPUs employed. This is because the Windows 2000
Server can't tell the difference between the logical and physical CPUs and it
can assign an additinal thread to a busy CPU.
By now I have already accomplished the migration using the script transfer
approach.
--
Many thanks,
Oskar
"Anthony Thomas" wrote:
> Can you do it? Sure. Is it a good idea or not? That depends on why you
> would want to do it. What are you trying to accomplish?
> Also, the weaker machine, you said, is only a 2-way CPU box, why would you
> have a 2 CPU affinity set on it?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:5DEC7960-CE31-4F0F-815F-E7B75BD3CFA4@.microsoft.com...
> Hi
> I have two machines one of which is 2 CPU, 3.5 GB RAM, HP Proliant DL 380
> G3 with MS Windows 2000 Advanced Server SP4 and MS SQL Server 2000 SP3 on
> it, the other - 4 CPU, 4 GB RAM, HP Proliant DL 580 G3 with MS Windows
> Server 2003 SP1 and MS SQL Server 2000 SP3.
> The SQL Server on the weaker machine has affinity mask turned on to use
> only 2 CPUs, dynamic memory allocation set on, master, and msdb databases
> located on drive E:.
> The SQL Server on the stronger machine has master and msdb located on
> drive C:, affinity mask set off, and dynamic memory allocation set on.
> Can I restore the master database from the weaker machine on the stronger
> machine and is it a good idea?
> --
> Many thanks,
> Oskar
>
>

restoring from tape to different server

hello all,
I preform regular sql server 2000 backups on our production server (Windows
2000 Server). I now need to restore, the Production DB to the backup server
(Windows 2000 Server) from tape (hp dds-4 data cartridge). The restore db
wizard (database radio button selected) should shows a list of all available
backups, but my backups to tape are not visible. Can someone explain this? I
know tape backups actually exist because I had verify backup selected and I
can see them on the production server.
When I select the "From Device" radio but on the wizard and then select my
tape drive everything is accepted, however everything locks up when I attempt
to "View Contents..." Any Ideas about that?
Please advise and remember I am a rookie?
much thanks
AndreAndre
Did you perform your backups direct to tape or did you do them to disk first
then copy to tape? If you did them to disk (the best way for speed and ease
of use), I suggest you copy them back to disk, then do you restore.
I'm afraid I don't know what your problem is if you performed your backups
direct to tape, as I have not done that since the days of version 6.5. Rather
than using EM, have you tried using query analyser, with the restore command?
HTH
John
"Andre Gibson" wrote:
> hello all,
> I preform regular sql server 2000 backups on our production server (Windows
> 2000 Server). I now need to restore, the Production DB to the backup server
> (Windows 2000 Server) from tape (hp dds-4 data cartridge). The restore db
> wizard (database radio button selected) should shows a list of all available
> backups, but my backups to tape are not visible. Can someone explain this? I
> know tape backups actually exist because I had verify backup selected and I
> can see them on the production server.
> When I select the "From Device" radio but on the wizard and then select my
> tape drive everything is accepted, however everything locks up when I attempt
> to "View Contents..." Any Ideas about that?
> Please advise and remember I am a rookie?
> much thanks
> Andre
>

Restoring from Multiple data sets

Running 2005, I have backups with multiple datasets on them.
But when I open the restore backup windows, it only shows me the last set.
How do I see the all the sets so I can choose which set to restore?
Thanks,
TomI don't understand the statement "backups with multiple datasets on them".
Do you mean you have made multiple backups to the same file? If so, did you
make sure you didn't INIT the file each time?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"tshad" <tshad@.dslextreme.com> wrote in message
news:upzCs2uqIHA.3616@.TK2MSFTNGP06.phx.gbl...
> Running 2005, I have backups with multiple datasets on them.
> But when I open the restore backup windows, it only shows me the last set.
> How do I see the all the sets so I can choose which set to restore?
> Thanks,
> Tom
>

Saturday, February 25, 2012

Restoring databases on SQL Server 2000 while trying not to restore to the wrong database

Experts,
Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a couple
of development teams using databases on the same SQL Server. While they can
backup their databases, they cannot restore their own databases. I have
noticed that the SQL server role overwrite the DB roles on each user
database. Users have to have DB creator permission in order to restore the
existing database. However, this role also grants users to ability to
restore DB to other users database's. Is there any way around this, so that
I could give my development users rights to restore THEIR OWN database but
not right to restore database created by someone else?
--
SpinHi
You could do this by letting them have their own instance, but then you may
as well get copies of developer edition for them!
Why do you not trust them?
John
"Spin" wrote:
> Experts,
> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a couple
> of development teams using databases on the same SQL Server. While they can
> backup their databases, they cannot restore their own databases. I have
> noticed that the SQL server role overwrite the DB roles on each user
> database. Users have to have DB creator permission in order to restore the
> existing database. However, this role also grants users to ability to
> restore DB to other users database's. Is there any way around this, so that
> I could give my development users rights to restore THEIR OWN database but
> not right to restore database created by someone else?
> --
> Spin
>
>|||I do not want them accidentally restoring onto someone else's database.
--
Spin
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:30C46FD5-B979-4B35-AEAE-0B6885F9EA57@.microsoft.com...
> Hi
> You could do this by letting them have their own instance, but then you
> may
> as well get copies of developer edition for them!
> Why do you not trust them?
> John
>
> "Spin" wrote:
>> Experts,
>> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a
>> couple
>> of development teams using databases on the same SQL Server. While they
>> can
>> backup their databases, they cannot restore their own databases. I have
>> noticed that the SQL server role overwrite the DB roles on each user
>> database. Users have to have DB creator permission in order to restore
>> the
>> existing database. However, this role also grants users to ability to
>> restore DB to other users database's. Is there any way around this, so
>> that
>> I could give my development users rights to restore THEIR OWN database
>> but
>> not right to restore database created by someone else?
>> --
>> Spin
>>|||Hi
Proper use of a source code contol system, and a regular backup regime for
you development server would reduce the potential for loss if this does
occur. Maybe you should allocate the privileges to more senior members of the
team only?
John
"Spin" wrote:
> I do not want them accidentally restoring onto someone else's database.
> --
> Spin
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:30C46FD5-B979-4B35-AEAE-0B6885F9EA57@.microsoft.com...
> > Hi
> >
> > You could do this by letting them have their own instance, but then you
> > may
> > as well get copies of developer edition for them!
> >
> > Why do you not trust them?
> >
> > John
> >
> >
> > "Spin" wrote:
> >
> >> Experts,
> >>
> >> Running Windows Server 2003 SP1 with SQL Server 2000 SP4. I have a
> >> couple
> >> of development teams using databases on the same SQL Server. While they
> >> can
> >> backup their databases, they cannot restore their own databases. I have
> >> noticed that the SQL server role overwrite the DB roles on each user
> >> database. Users have to have DB creator permission in order to restore
> >> the
> >> existing database. However, this role also grants users to ability to
> >> restore DB to other users database's. Is there any way around this, so
> >> that
> >> I could give my development users rights to restore THEIR OWN database
> >> but
> >> not right to restore database created by someone else?
> >>
> >> --
> >> Spin
> >>
> >>
> >>
>
>

Restoring Databases from Win2000 to Win2003/Collation

Default Collation is as follows:-

SQL Server 2000 on Windows 2000: SQL_Latin1_General_CP1_CI_AS
SQL Server 2000 on Windows Server 2003: Latin1_General_CI_AS

Databases restored from the Windows 2000 Server to Windows Server 2003 have a different collation than what the Windows Server 2003s collation is.

Does anyone know if this new collation is a permanent change for Microsoft and Windows/SQL?

Has anybody figured out a way of changing the collation of a database without having to rebuild it into a new database or by rebuilding the master?

Any other work arounds?The attached stored procedure will generate a change script that will recollate a database. Check the script comments for known limitations. You can run this script from query analyser.

Essentially this generates a change script that: drops all indexes, constraints and statistics on columns that don't have the desired target collation. Alters the columns to the new collation, alters the database to the new collation, and replaces all the indexes, constraints and statistics removed in the first place.

I'm attaching the file in the message reply window. I hope it works.

HH

Tuesday, February 21, 2012

Restoring database to Win 2003 Server

We are restoring a database to a Windows 2003 Server. After the install it
created a Data folder at E:\Microsoft SQL Server. I'm a local admin on the
machine and yet whenever I try to drill down into E:\Microsoft SQL
Server\MSSQL\, it gives me the error message "E:\Microsoft SQL Server\MSSQL
is not accessible. Access is denied."
I was hoping to create several subdirectories in this folder to structure
how our database .mdf files are structured. Suggestions? Am I missing
something? Is there something about SQL Server on 2003 that we should be
aware of?
Thanks in advance!
Mark
field027@.umn.eduMy guess is that the SQL Server service account lacks some permission on
that drive/directory.
--
Tibor Karaszi
"Mark" <mfield@.idonotlikespam.cce.umn.edu> wrote in message
news:ubJmEvkoDHA.2188@.TK2MSFTNGP11.phx.gbl...
> We are restoring a database to a Windows 2003 Server. After the install
it
> created a Data folder at E:\Microsoft SQL Server. I'm a local admin on
the
> machine and yet whenever I try to drill down into E:\Microsoft SQL
> Server\MSSQL\, it gives me the error message "E:\Microsoft SQL
Server\MSSQL
> is not accessible. Access is denied."
> I was hoping to create several subdirectories in this folder to structure
> how our database .mdf files are structured. Suggestions? Am I missing
> something? Is there something about SQL Server on 2003 that we should be
> aware of?
> Thanks in advance!
> Mark
> field027@.umn.edu
>

Friday, March 30, 2012

Restrict users to modify tabble structure

Restrict users to modify tabble structure

Restrict users to modify tabble structure

Monday, March 26, 2012

Restoring the master to different drive letters

Wednesday, March 21, 2012

restoring SQL 2000 on Windows 2000

restoring SQL 2000 on Windows 2000

restoring SQL 2000 on Windows 2000

Monday, March 12, 2012

Restoring Master database

Restoring Master database

Restoring Master database

Restoring master and msdb on a different server

Restoring master and msdb on a different server

Friday, March 9, 2012

Restoring master and msdb on a different server

restoring from tape to different server

Restoring from Multiple data sets

Saturday, February 25, 2012

Restoring databases on SQL Server 2000 while trying not to restore to the wrong database

Restoring Databases from Win2000 to Win2003/Collation

Tuesday, February 21, 2012

Restoring database to Win 2003 Server

database problem

Blog Archive

About Me