Mirroring between Standard and Enterprise editions...

Hi All,

We are going to use database mirroring and database snapshots for reporting. The principal server runs SQL Server 2005 Standard Edition and mirror (reporting) runs SQL Server 2005 Enterprise Edition (64-bit). I failed to setup database mirroring trough GUI using SQL Server Management Studio and got this error:

This mirroring configuration is not supported. Because the principal server instance, <server_name>, is Standard Edition, the mirror server instance must also be Standard Edition.

But when I use T-SQL commands I was able to setup database mirroring and it works OK so far.

SQL BOL says that one of requirements for database mirroring is to use the same SQL Server editions but I am wondering if it works trough T-SQL why MS mention it in the requirements list, also is totally unsupported by MS?

Thanks

Oleg

Oleg,

While this will probably work fine, we don't test this combination internally. If you mirror from a principal that is STD edition to a mirror that is EE edition, it would probably work without issues. Mirroring the other way (from EE to STD) could be problematic because of the EE features that are not present in STD. Since mirroring supports failover and failback, in theory it is possible for you to be in the situation where you are mirroring from EE->STD edition even if that is not the initial configuarion.

Regards,

Matt Hollingsworth

Program Manager, SQL Server High Availability

|||

Matt,

Thanks for your answer.

Our plan is to use database mirroring only for reporting and not for high availability. (We use replication and remote DC for HA). So mirroring from Standard to Enterprise Edition will be the only one scenario that we going to use option in our reporting environment.
The concern that we have is if we will be able to use mirroring between Standard and Enterprise in the future releases of SP2, SP3.

Thanks Oleg

|||

I am curious to why you want EE on the mirror server?

Only because the database snapshot feature?

Actually this is very similiar to what we need (use mirroring mostly for reports, not for HA) but since we don't have EE, we actually setup 2 STD instances on the mirror server

Server1 <- live server

Server2\Mirror <- mirrored, can be automatic fail over

Server2\Log <- log shipping, used for reports

Server3 <- witness and log shipping monitor server

Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

Does that mean we can use EE with snapshot on Server2 without having to pay a license?

Thanks

|||

Yes we are going to use EE edition only for reporting since it doesn't require extra support efforts and also we can have a fair data refresh latency.
For the stand-by server you don't have to pay for licensing and it's valid for cluster or mirroring unless you also going to use it also for reporting.

tnx.

I'm closing this topic, thanks to all for answers and inputs............OH

|||

>> Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

No, it doesn't. This only applies if you are using the 2nd server for failover only. By creating snapshots and running reporting off of it, it is no longer a failover only server.

Also, in order to cover both servers under 1 license, the license has to be valid for each server. So, you would have to run both under an Enterprise license, not a standard license.

Mirroring between Standard and Enterprise editions...

Hi All,

We are going to use database mirroring and database snapshots for reporting. The principal server runs SQL Server 2005 Standard Edition and mirror (reporting) runs SQL Server 2005 Enterprise Edition (64-bit). I failed to setup database mirroring trough GUI using SQL Server Management Studio and got this error:

This mirroring configuration is not supported. Because the principal server instance, <server_name>, is Standard Edition, the mirror server instance must also be Standard Edition.

But when I use T-SQL commands I was able to setup database mirroring and it works OK so far.

SQL BOL says that one of requirements for database mirroring is to use the same SQL Server editions but I am wondering if it works trough T-SQL why MS mention it in the requirements list, also is totally unsupported by MS?

Thanks

Oleg

Oleg,

While this will probably work fine, we don't test this combination internally. If you mirror from a principal that is STD edition to a mirror that is EE edition, it would probably work without issues. Mirroring the other way (from EE to STD) could be problematic because of the EE features that are not present in STD. Since mirroring supports failover and failback, in theory it is possible for you to be in the situation where you are mirroring from EE->STD edition even if that is not the initial configuarion.

Regards,

Matt Hollingsworth

Program Manager, SQL Server High Availability

|||

Matt,

Thanks for your answer.

Our plan is to use database mirroring only for reporting and not for high availability. (We use replication and remote DC for HA). So mirroring from Standard to Enterprise Edition will be the only one scenario that we going to use option in our reporting environment.
The concern that we have is if we will be able to use mirroring between Standard and Enterprise in the future releases of SP2, SP3.

Thanks Oleg

|||

I am curious to why you want EE on the mirror server?

Only because the database snapshot feature?

Actually this is very similiar to what we need (use mirroring mostly for reports, not for HA) but since we don't have EE, we actually setup 2 STD instances on the mirror server

Server1 <- live server

Server2\Mirror <- mirrored, can be automatic fail over

Server2\Log <- log shipping, used for reports

Server3 <- witness and log shipping monitor server

Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

Does that mean we can use EE with snapshot on Server2 without having to pay a license?

Thanks

|||

Yes we are going to use EE edition only for reporting since it doesn't require extra support efforts and also we can have a fair data refresh latency.
For the stand-by server you don't have to pay for licensing and it's valid for cluster or mirroring unless you also going to use it also for reporting.

tnx.

I'm closing this topic, thanks to all for answers and inputs............OH

|||

>> Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

No, it doesn't. This only applies if you are using the 2nd server for failover only. By creating snapshots and running reporting off of it, it is no longer a failover only server.

Also, in order to cover both servers under 1 license, the license has to be valid for each server. So, you would have to run both under an Enterprise license, not a standard license.

Minimum Install MSI for SQL Server 2005

Off of the MSDN SQL Server 2005 Enterprise Edition, what is the MSI I should use to install SQL Server 2005.

I have to Upload all files to a server, and this is going to be painfully slow. Can anyone tell me what the minimum is to upload and install SQL Server Enterprise (not Express)?

(For 32 and 64 bit non-Itanium machines)

That partially depends upon what functionality you intend to install.

MSSQL SSIS AS NS BIDS SSMS Other Client tools|||MSSQL
SSIS
and Reporting Services.
|||

Calling the MSIs directly is not a supported install method. You need to go through setup.exe to install the product.

Thanks,
Sam Lester (MSFT)

|||Does this mean my only choice to get these set up is to upload the entire 985 Meg on each and every server I need to install this on?
|||

Nope, you don't need to copy the files to each machine. You can copy it to a network location and run that install from each machine or you could insert the cd/dvd's into each local machine. The most common approach is probably to copy it to a network share and run the setup.exe from there.

Thanks,
Sam

|||If you have Dedicated Hosted Internet Servers, what are the options?

I don't have physical access to the machine. And I don't have access to an internal Microsoft network to create a Network install.

This is for an Internet Service Provider that is hosting the machine, and our access to it is primarily through Remote Desktop, and FTP.

Can one do a Network Install, and then copy up a smaller file signature to the hosted server?

Otherwise I'm looking at a 800Meg + Upload for EACH machine I need to install this on.
|||** bumpsql

Minimum Install MSI for SQL Server 2005

Off of the MSDN SQL Server 2005 Enterprise Edition, what is the MSI I should use to install SQL Server 2005.

I have to Upload all files to a server, and this is going to be painfully slow. Can anyone tell me what the minimum is to upload and install SQL Server Enterprise (not Express)?

(For 32 and 64 bit non-Itanium machines)

That partially depends upon what functionality you intend to install.

MSSQL SSIS AS NS BIDS SSMS Other Client tools|||MSSQL
SSIS
and Reporting Services.
|||

Calling the MSIs directly is not a supported install method. You need to go through setup.exe to install the product.

Thanks,
Sam Lester (MSFT)

|||Does this mean my only choice to get these set up is to upload the entire 985 Meg on each and every server I need to install this on?
|||

Nope, you don't need to copy the files to each machine. You can copy it to a network location and run that install from each machine or you could insert the cd/dvd's into each local machine. The most common approach is probably to copy it to a network share and run the setup.exe from there.

Thanks,
Sam

|||If you have Dedicated Hosted Internet Servers, what are the options?

I don't have physical access to the machine. And I don't have access to an internal Microsoft network to create a Network install.

This is for an Internet Service Provider that is hosting the machine, and our access to it is primarily through Remote Desktop, and FTP.

Can one do a Network Install, and then copy up a smaller file signature to the hosted server?

Otherwise I'm looking at a 800Meg + Upload for EACH machine I need to install this on.
|||** bump

Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

Hi
I wan to migrate an SQL Enterprise server system to SQL Standard system.
Can somebody guide me throgh the process?
Thanks
KND
Hi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migraton from Enterprise to Standard

H
I wan to migrate an SQL Enterprise server system to SQL Standard system
Can somebody guide me throgh the process
Thank
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migration to MySQL?

From a "price point of view" migrating from the actual platform (2 node
cluster Windows server 2003 with SQL Server 2000 Enterprise Edition)to MySQL
can be very attractive.
In fact our management starts to think that way...
My question is related to the faisability of this operation in a critical
production cluster server.
Is it recommanded?
Pros and Cons?
Why yes and why no.
Please advise.
Franco
It is difficult to answer this type of questions rigorously in a newsgroup
forum. I'd suggest that you invole all the stakeholders and conduct a
comparative risk analysis on the migration. The compartive risk analysis
should cover the key risk factors that are important to your organizaton.
Note that cost factors are but one category among many others.
Some of risk factors to consider include reliability and resilience (e.g.
high availability, stability of the DBMS, proven platform, etc), scalability
and performance (e.g. scalability in terms of database size, # of processors,
memory size, partitioning, index maintenance, etc), manageability (e.g. ease
of backup/restore), operations issus (e.g. need for consistency checks,
availability of expetise, monitoring tools, etc), portfolio impact (e.g. what
is the mix of your installed DBMS and apps using various DBMS, dependencies
among the databases, etc), and supportability (e.g. vendor support, user
community, etc). Obviously, you would have to rate these and other factors
per their relative importance to your apps and organization.
Linchi
"Franco" wrote:

> From a "price point of view" migrating from the actual platform (2 node
> cluster Windows server 2003 with SQL Server 2000 Enterprise Edition)to MySQL
> can be very attractive.
> In fact our management starts to think that way...
> My question is related to the faisability of this operation in a critical
> production cluster server.
> Is it recommanded?
> Pros and Cons?
> Why yes and why no.
> Please advise.
> --
> Franco

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advance
Backup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegr oups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advanceHi
I would expect this to work are you having problems?
John
"luca drink" wrote:
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>|||Backup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegroups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advanceBackup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegroups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Serv

We are migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)

Problem :

- The performance difference observer was not much (Just 15-18%)

- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%

- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.

Steps followed for Migration:

- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).

- We ran the DBCC DBREINDEX for each affected tables

- We executed the sp_updatestats procedure for all the tables

- Upgraded the DB compatibility version to 90

- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.

One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.

A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.

The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.

Also

when we run this query

select * from sys.dm_os_sys_info

one column os_priority_class shows a value = 32 ? what does this means.

In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value

Advanced > Running Under 64 bit OS = No ? what does this means.

Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.

Hi Ashok,

Running Under 64 bit OS =No means that Operating System is not 64 bit version, you are running 64 bit Version of SQL Server on Operating System which is 32 bit.

Regarding SQL Server Memory it is Dynamically Allocated and De Allocated unless you have specified using sp_configure or via SSMS, another thing you need to refer is have you or some one change the values for network packet size / Min memory / maximum memory value

have you set any option for max degree of parallelism Or max worker threads

If you do have more then 2 GB memory you need to use AWE OR PAE switch in order to use memory more then 2 GB , also refer Estimated and Actual Exucution Plan in both the server to get idea for taking too much time in new server.

Refer http://www.sql-server-performance.com/statistics_io_time.asp

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17451

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17732

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=18192

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17107

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=16988

HTH
Hemantgiri S. Goswami

Migration from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium

We are migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)

Problem :

- The performance difference observer was not much (Just 15-18%)

- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%

- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.

Steps followed for Migration:

- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).

- We ran the DBCC DBREINDEX for each affected tables

- We executed the sp_updatestats procedure for all the tables

- Upgraded the DB compatibility version to 90

- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.

One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.

A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.

The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.

Also

when we run this query

select * from sys.dm_os_sys_info

one column os_priority_class shows a value = 32 ? what does this means.

In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value

Advanced > Running Under 64 bit OS = No ? what does this means.

Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.

Hi Ashok,

Running Under 64 bit OS =No means that Operating System is not 64 bit version, you are running 64 bit Version of SQL Server on Operating System which is 32 bit.

Regarding SQL Server Memory it is Dynamically Allocated and De Allocated unless you have specified using sp_configure or via SSMS, another thing you need to refer is have you or some one change the values for network packet size / Min memory / maximum memory value

have you set any option for max degree of parallelism Or max worker threads

If you do have more then 2 GB memory you need to use AWE OR PAE switch in order to use memory more then 2 GB , also refer Estimated and Actual Exucution Plan in both the server to get idea for taking too much time in new server.

Refer http://www.sql-server-performance.com/statistics_io_time.asp

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17451

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17732

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=18192

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17107

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=16988

HTH
Hemantgiri S. Goswami

Migrating to new domain

We are migrating to a new domain. Some clients running SQL Enterprise manag
er have been migrated to a different domain than the one the actually SQL se
rver is in. When the clients were migrated they had to reregister their ser
vers in Enterprise manager.
Where is the list of servers stored that the client had registered? Registr
y key perhaps? If so which one? I would like to retain the list that the c
lient had registered or at least be able to tell them where they can get the
list.
I can retrieve a list of servers via sqldmo but only ones that are in the ne
w domain because my machine exist in the new domain.
Any help would be appreciated.GG wrote:

> We are migrating to a new domain. Some clients running SQL
> Enterprise manager have been migrated to a different domain than the
> one the actually SQL server is in. When the clients were migrated
> they had to reregister their servers in Enterprise manager. Where is
> the list of servers stored that the client had registered? Registry
> key perhaps? If so which one? I would like to retain the list that
> the client had registered or at least be able to tell them where they
> can get the list.
> I can retrieve a list of servers via sqldmo but only ones that are in
> the new domain because my machine exist in the new domain.
The SQL Servers groups with registered servers lists are usually stored in
HKCU\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered
Servers X
But I am not sure whether you can just export/import the registry keys to
the different domain, never tried this.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank You Sabastian. That is a start. Much appreciated.