hi,
the virtual sql servers are sharing the same windwos RAM memory, utilize
processor(s) and Disk IO?
What's is the diff between creating virtual sql servers and adding more sql
instances in one sql server?
1. each Virtual server need sql and windows licenses. sql instanses no need
additional one.
THnaks
If you create two virtual servers, then you need ram for two operating
systems as well as SQL Server. If you create two named instance on one
virtual server, then ram is needed for one operating system, and two sql
servers.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"mecn" wrote:
> hi,
> the virtual sql servers are sharing the same windwos RAM memory, utilize
> processor(s) and Disk IO?
> What's is the diff between creating virtual sql servers and adding more sql
> instances in one sql server?
> 1. each Virtual server need sql and windows licenses. sql instanses no need
> additional one.
> THnaks
>
>
>
>
sql
Showing posts with label disk. Show all posts
Showing posts with label disk. Show all posts
Thursday, March 22, 2012
adding 2 or more vitural machines for sql server.
hi,
the virtual sql servers are sharing the same windwos RAM memory, utilize
processor(s) and Disk IO?
What's is the diff between creating virtual sql servers and adding more sql
instances in one sql server?
1. each Virtual server need sql and windows licenses. sql instanses no need
additional one.
THnaksIf you create two virtual servers, then you need ram for two operating
systems as well as SQL Server. If you create two named instance on one
virtual server, then ram is needed for one operating system, and two sql
servers.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"mecn" wrote:
> hi,
> the virtual sql servers are sharing the same windwos RAM memory, utilize
> processor(s) and Disk IO?
> What's is the diff between creating virtual sql servers and adding more sql
> instances in one sql server?
> 1. each Virtual server need sql and windows licenses. sql instanses no need
> additional one.
> THnaks
>
>
>
>
the virtual sql servers are sharing the same windwos RAM memory, utilize
processor(s) and Disk IO?
What's is the diff between creating virtual sql servers and adding more sql
instances in one sql server?
1. each Virtual server need sql and windows licenses. sql instanses no need
additional one.
THnaksIf you create two virtual servers, then you need ram for two operating
systems as well as SQL Server. If you create two named instance on one
virtual server, then ram is needed for one operating system, and two sql
servers.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"mecn" wrote:
> hi,
> the virtual sql servers are sharing the same windwos RAM memory, utilize
> processor(s) and Disk IO?
> What's is the diff between creating virtual sql servers and adding more sql
> instances in one sql server?
> 1. each Virtual server need sql and windows licenses. sql instanses no need
> additional one.
> THnaks
>
>
>
>
Tuesday, March 20, 2012
adding 2 or more vitural machines for sql server.
hi,
the virtual sql servers are sharing the same windwos RAM memory, utilize
processor(s) and Disk IO?
What's is the diff between creating virtual sql servers and adding more sql
instances in one sql server?
1. each Virtual server need sql and windows licenses. sql instanses no need
additional one.
THnaksIf you create two virtual servers, then you need ram for two operating
systems as well as SQL Server. If you create two named instance on one
virtual server, then ram is needed for one operating system, and two sql
servers.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"mecn" wrote:
> hi,
> the virtual sql servers are sharing the same windwos RAM memory, utilize
> processor(s) and Disk IO?
> What's is the diff between creating virtual sql servers and adding more sq
l
> instances in one sql server?
> 1. each Virtual server need sql and windows licenses. sql instanses no nee
d
> additional one.
> THnaks
>
>
>
>
the virtual sql servers are sharing the same windwos RAM memory, utilize
processor(s) and Disk IO?
What's is the diff between creating virtual sql servers and adding more sql
instances in one sql server?
1. each Virtual server need sql and windows licenses. sql instanses no need
additional one.
THnaksIf you create two virtual servers, then you need ram for two operating
systems as well as SQL Server. If you create two named instance on one
virtual server, then ram is needed for one operating system, and two sql
servers.
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"mecn" wrote:
> hi,
> the virtual sql servers are sharing the same windwos RAM memory, utilize
> processor(s) and Disk IO?
> What's is the diff between creating virtual sql servers and adding more sq
l
> instances in one sql server?
> 1. each Virtual server need sql and windows licenses. sql instanses no nee
d
> additional one.
> THnaks
>
>
>
>
added memory - disk now full
We have a win 2000 server with SQL Server 2K.
Over the weekend, they added 4GB of RAM to the existing 4GB.
They did not enable AWE, nor /PAE /3GB. THat is planned for after an upgrade to 2003, this was in theory just to get the hardware stuff out of the way.
When I left on friday, there was 3.5GB on our data drive, which is typical although much too low. (we are also adding space to the SAN next weekend)
The problem is, when I came in this morning, there was only 9MB left on our data drive. I did request that they run update useage on the main database, but that would only help matters, wouldn't it?
Could the disk space problem be due to the memory addition?
Physical memory is paged in and out from and to the paging file. If you system is setup so the paging file size is system managed, the paging file size will be ~150-300% of physical ram. Adding 4 GB of RAM would have increased the paging file size by quite a bit, hence the change in free disk space.|||IMO, a system with 8GB of memory should disable paging. That is not a widely-shared point of view, however. I disable paging on my 2GB dev. system.Sunday, March 11, 2012
Add SAN Disk Resource to Active/Active SQL cluster
Looking to see if I am missing any steps below to adding a SAN disk
resource to an Active/Active SQL cluster:
-Create Volumes
-Present LUNs to both Nodes
-Failover Cluster Groups to Node2
-On Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node1
Rescan for hardware changes
Write the disk signature
Set disk to basic
Create Partition
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node1
-On Node2
Failover Cluster Groups to Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node2
Rescan for hardware changes
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node2
-Assign disk resource to Cluster Groups
-On Node1
Take SQL Server Resource offline
Add SQL Server Resource dependency to disk resource
Bring SQL Server Resource online
-On Node2
Repeat above
-Test failover
Thanks,
Ian in SD
With Windows 2003 as the host, you may be able to skip some of the reboots.
You can rescan the disk list and pick up newly added disks. I have never
had to disable or stop the cluster service to pick up new disks. I do make
sure and do all the work on a node that does not currently host any cluster
resources. Once I am done, I can rescan the disk list on the other node(s)
and failover at will. If you have the downtime, the reboots won't hurt, but
they may not be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<theredmiata@.hotmail.com> wrote in message
news:1142967852.423752.294080@.i39g2000cwa.googlegr oups.com...
> Looking to see if I am missing any steps below to adding a SAN disk
> resource to an Active/Active SQL cluster:
>
> -Create Volumes
> -Present LUNs to both Nodes
> -Failover Cluster Groups to Node2
> -On Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node1
> Rescan for hardware changes
> Write the disk signature
> Set disk to basic
> Create Partition
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node1
> -On Node2
> Failover Cluster Groups to Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node2
> Rescan for hardware changes
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node2
> -Assign disk resource to Cluster Groups
> -On Node1
> Take SQL Server Resource offline
> Add SQL Server Resource dependency to disk resource
> Bring SQL Server Resource online
> -On Node2
> Repeat above
> -Test failover
> Thanks,
> Ian in SD
>
|||Thanks for the reply Geoff. This the first time for this process as we
are trying to split the file groups and would like to have each group
on a seperate volume.
resource to an Active/Active SQL cluster:
-Create Volumes
-Present LUNs to both Nodes
-Failover Cluster Groups to Node2
-On Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node1
Rescan for hardware changes
Write the disk signature
Set disk to basic
Create Partition
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node1
-On Node2
Failover Cluster Groups to Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node2
Rescan for hardware changes
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node2
-Assign disk resource to Cluster Groups
-On Node1
Take SQL Server Resource offline
Add SQL Server Resource dependency to disk resource
Bring SQL Server Resource online
-On Node2
Repeat above
-Test failover
Thanks,
Ian in SD
With Windows 2003 as the host, you may be able to skip some of the reboots.
You can rescan the disk list and pick up newly added disks. I have never
had to disable or stop the cluster service to pick up new disks. I do make
sure and do all the work on a node that does not currently host any cluster
resources. Once I am done, I can rescan the disk list on the other node(s)
and failover at will. If you have the downtime, the reboots won't hurt, but
they may not be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<theredmiata@.hotmail.com> wrote in message
news:1142967852.423752.294080@.i39g2000cwa.googlegr oups.com...
> Looking to see if I am missing any steps below to adding a SAN disk
> resource to an Active/Active SQL cluster:
>
> -Create Volumes
> -Present LUNs to both Nodes
> -Failover Cluster Groups to Node2
> -On Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node1
> Rescan for hardware changes
> Write the disk signature
> Set disk to basic
> Create Partition
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node1
> -On Node2
> Failover Cluster Groups to Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node2
> Rescan for hardware changes
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node2
> -Assign disk resource to Cluster Groups
> -On Node1
> Take SQL Server Resource offline
> Add SQL Server Resource dependency to disk resource
> Bring SQL Server Resource online
> -On Node2
> Repeat above
> -Test failover
> Thanks,
> Ian in SD
>
|||Thanks for the reply Geoff. This the first time for this process as we
are trying to split the file groups and would like to have each group
on a seperate volume.
Friday, February 24, 2012
add disk to a cluster running sql2005
hi,
I have a windows 2003 sp1 cluster running sql2005.
the DB is installed on S: and i have a R: & U: drive letter that is both
differend disk and runs fine in the cluster.
But i can not see those disks in sql 2005 why ?
the disks are in the same resource group (SQL)
where can I choose the R drive ?
if I choose attach DB I see only the S drive where the DB is installed.
any help is welcome
greetings,
Robert
Hi,
Just fixed it
I added the disk resources to the SQL2005 server resource and now it is
running.
greetings,
"Robert Smit ( 450331)" <RSM.news@.thebackbone.nl> wrote in message
news:OeiQZhQFGHA.524@.TK2MSFTNGP09.phx.gbl...
> hi,
> I have a windows 2003 sp1 cluster running sql2005.
> the DB is installed on S: and i have a R: & U: drive letter that is both
> differend disk and runs fine in the cluster.
> But i can not see those disks in sql 2005 why ?
> the disks are in the same resource group (SQL)
> where can I choose the R drive ?
> if I choose attach DB I see only the S drive where the DB is installed.
> any help is welcome
> greetings,
> Robert
>
|||Just adding them to the SQL Server group is not enough. They have to be
added as a dependency of the SQL Server resource.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Robert Smit ( 450331)" <RSM.news@.thebackbone.nl> wrote in message
news:OeiQZhQFGHA.524@.TK2MSFTNGP09.phx.gbl...
> hi,
> I have a windows 2003 sp1 cluster running sql2005.
> the DB is installed on S: and i have a R: & U: drive letter that is both
> differend disk and runs fine in the cluster.
> But i can not see those disks in sql 2005 why ?
> the disks are in the same resource group (SQL)
> where can I choose the R drive ?
> if I choose attach DB I see only the S drive where the DB is installed.
> any help is welcome
> greetings,
> Robert
>
I have a windows 2003 sp1 cluster running sql2005.
the DB is installed on S: and i have a R: & U: drive letter that is both
differend disk and runs fine in the cluster.
But i can not see those disks in sql 2005 why ?
the disks are in the same resource group (SQL)
where can I choose the R drive ?
if I choose attach DB I see only the S drive where the DB is installed.
any help is welcome
greetings,
Robert
Hi,
Just fixed it
I added the disk resources to the SQL2005 server resource and now it is
running.
greetings,
"Robert Smit ( 450331)" <RSM.news@.thebackbone.nl> wrote in message
news:OeiQZhQFGHA.524@.TK2MSFTNGP09.phx.gbl...
> hi,
> I have a windows 2003 sp1 cluster running sql2005.
> the DB is installed on S: and i have a R: & U: drive letter that is both
> differend disk and runs fine in the cluster.
> But i can not see those disks in sql 2005 why ?
> the disks are in the same resource group (SQL)
> where can I choose the R drive ?
> if I choose attach DB I see only the S drive where the DB is installed.
> any help is welcome
> greetings,
> Robert
>
|||Just adding them to the SQL Server group is not enough. They have to be
added as a dependency of the SQL Server resource.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Robert Smit ( 450331)" <RSM.news@.thebackbone.nl> wrote in message
news:OeiQZhQFGHA.524@.TK2MSFTNGP09.phx.gbl...
> hi,
> I have a windows 2003 sp1 cluster running sql2005.
> the DB is installed on S: and i have a R: & U: drive letter that is both
> differend disk and runs fine in the cluster.
> But i can not see those disks in sql 2005 why ?
> the disks are in the same resource group (SQL)
> where can I choose the R drive ?
> if I choose attach DB I see only the S drive where the DB is installed.
> any help is welcome
> greetings,
> Robert
>
Thursday, February 16, 2012
Add a new disk
Since the existing disk is almost full, we are going to
add an additional disk to the SQL Server 2000.
We would like to move all SQL Server Backup files to the
new disk. We would like to know what we have to do is as
follow:
1) Add a new disk (With a different drive name)
2) Copy the whole folder of "data\MSSQL\BACKUP" to the new
drive
3) Change the Directory used for backup in the Database
Maintenance Plan
ThanksI wouldn't move the folder. I'd just create the desired folder on the new
drive and specify this as the backup directory in your jobs/plane, and then
for a few days clean up the old backup files manually.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:0eb501c3c046$d9917c60$a001280a@.phx.gbl...
> Since the existing disk is almost full, we are going to
> add an additional disk to the SQL Server 2000.
> We would like to move all SQL Server Backup files to the
> new disk. We would like to know what we have to do is as
> follow:
> 1) Add a new disk (With a different drive name)
> 2) Copy the whole folder of "data\MSSQL\BACKUP" to the new
> drive
> 3) Change the Directory used for backup in the Database
> Maintenance Plan
> Thanks
add an additional disk to the SQL Server 2000.
We would like to move all SQL Server Backup files to the
new disk. We would like to know what we have to do is as
follow:
1) Add a new disk (With a different drive name)
2) Copy the whole folder of "data\MSSQL\BACKUP" to the new
drive
3) Change the Directory used for backup in the Database
Maintenance Plan
ThanksI wouldn't move the folder. I'd just create the desired folder on the new
drive and specify this as the backup directory in your jobs/plane, and then
for a few days clean up the old backup files manually.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:0eb501c3c046$d9917c60$a001280a@.phx.gbl...
> Since the existing disk is almost full, we are going to
> add an additional disk to the SQL Server 2000.
> We would like to move all SQL Server Backup files to the
> new disk. We would like to know what we have to do is as
> follow:
> 1) Add a new disk (With a different drive name)
> 2) Copy the whole folder of "data\MSSQL\BACKUP" to the new
> drive
> 3) Change the Directory used for backup in the Database
> Maintenance Plan
> Thanks
Subscribe to:
Posts (Atom)