Migrating to SQL 2005: running

Showing posts with label running. Show all posts

Friday, March 30, 2012

Mirroring and 64 vs 32 bit performance

Hi,
I have a few questions regarding sql server 2005 .
Hardware will be running with a single dual core 64 bit Opteron 175.
1) Are there any performance advantages running sql 2005 Workgroup Edition
on Windows 2003 64 bit Edition? If so what are they?
2) Are there any benchmarks on how much faster sql 2005 Standard Edition vs
sql 2005 Workgroup Edition runs on Windows 2003 64 bit Edition?
3) For sql 2005 Standard Edition and the database mirroring functionality :
is it possible to mirror multiple sql servers to just one failover mirror or
do you need a separate sql box to mirror each one ?
Thanks"greg" <greg_platt@.hotmail.com> wrote in message
news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
> Hi,
> I have a few questions regarding sql server 2005 .
> Hardware will be running with a single dual core 64 bit Opteron 175.
> 1) Are there any performance advantages running sql 2005 Workgroup Edition
> on Windows 2003 64 bit Edition? If so what are they?
>
Yes. Workgroup Edition only comes in 32bit and can only use 3GB of RAM, and
lacks the tuning tools of SQL Server.
> 2) Are there any benchmarks on how much faster sql 2005 Standard Edition
> vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit Edition?
No. For small workloads there shouldn't be much difference.
> 3) For sql 2005 Standard Edition and the database mirroring functionality
> : is it possible to mirror multiple sql servers to just one failover
> mirror or do you need a separate sql box to mirror each one ?
>
One mirror per database, although the mirror server can mirror multiple
databases.
David|||Thanks David,
So for 1) i'm not sure you've answered the question. I know Workgroup
Edition is 32bit but it can run on Windows 2003 Standard 64bit edition using
WOW. Now because i have a 64bit Opteron will i see SQL run quicker in this
config as opposed to using Windows 2003 Standard 32bit Server? Also are
there any performance penalties using WOW?
For 3) i take it you mean you can only have one prinicipal server per
mirror?
So if i have two SQL server machines running different databases and i need
to use just 1 backup server incase one machine fails what are my best
options?
Log-Shipping? or Replication?
Clustering would be too expensive for us and Mirroring would also be too
expensive if you need one mirror for each SQL server machine.
Thanks.
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:%237r4ZseGGHA.1032@.TK2MSFTNGP15.phx.gbl...
> "greg" <greg_platt@.hotmail.com> wrote in message
> news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a few questions regarding sql server 2005 .
>> Hardware will be running with a single dual core 64 bit Opteron 175.
>> 1) Are there any performance advantages running sql 2005 Workgroup
>> Edition on Windows 2003 64 bit Edition? If so what are they?
> Yes. Workgroup Edition only comes in 32bit and can only use 3GB of RAM,
> and lacks the tuning tools of SQL Server.
>
>> 2) Are there any benchmarks on how much faster sql 2005 Standard Edition
>> vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit Edition?
> No. For small workloads there shouldn't be much difference.
>> 3) For sql 2005 Standard Edition and the database mirroring functionality
>> : is it possible to mirror multiple sql servers to just one failover
>> mirror or do you need a separate sql box to mirror each one ?
> One mirror per database, although the mirror server can mirror multiple
> databases.
> David
>|||Most of the benefits of 64 bit architectures are a result of the flat memory
space but Workgroup Edition is not going to be able to take advantage of
most of that. running a 32 bit edition in WOW allows 4 GB of user space so
there is some advantage there. Currently, 64 bit processors are generally
slower than the fastest 32 bit processors so in some cases a 32 bit
processor might actually give better performance than a 64 bit processor and
WOW. Of course, with a 64 bit machine you have the advantage of being able
to upgrade to Standard edition and take advantage of the flat memory space
if you run out of horsepower in WOW.
You can have multiple servers mirrored to a single DB Mirroring server
because individual databases are mirrored. You would have to be careful to
ensure that the mirror has enough resources to both handle the load of
mirroring databases from several server and the load of running the
databases when they're failed over.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"greg" <greg_platt@.hotmail.com> wrote in message
news:uBwm4ejGGHA.3916@.TK2MSFTNGP10.phx.gbl...
> Thanks David,
> So for 1) i'm not sure you've answered the question. I know Workgroup
> Edition is 32bit but it can run on Windows 2003 Standard 64bit edition
> using WOW. Now because i have a 64bit Opteron will i see SQL run quicker
> in this config as opposed to using Windows 2003 Standard 32bit Server?
> Also are there any performance penalties using WOW?
> For 3) i take it you mean you can only have one prinicipal server per
> mirror?
> So if i have two SQL server machines running different databases and i
> need to use just 1 backup server incase one machine fails what are my best
> options?
> Log-Shipping? or Replication?
> Clustering would be too expensive for us and Mirroring would also be too
> expensive if you need one mirror for each SQL server machine.
> Thanks.
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:%237r4ZseGGHA.1032@.TK2MSFTNGP15.phx.gbl...
>> "greg" <greg_platt@.hotmail.com> wrote in message
>> news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a few questions regarding sql server 2005 .
>> Hardware will be running with a single dual core 64 bit Opteron 175.
>> 1) Are there any performance advantages running sql 2005 Workgroup
>> Edition on Windows 2003 64 bit Edition? If so what are they?
>>
>> Yes. Workgroup Edition only comes in 32bit and can only use 3GB of RAM,
>> and lacks the tuning tools of SQL Server.
>>
>> 2) Are there any benchmarks on how much faster sql 2005 Standard Edition
>> vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit Edition?
>> No. For small workloads there shouldn't be much difference.
>> 3) For sql 2005 Standard Edition and the database mirroring
>> functionality : is it possible to mirror multiple sql servers to just
>> one failover mirror or do you need a separate sql box to mirror each one
>> ?
>>
>> One mirror per database, although the mirror server can mirror multiple
>> databases.
>> David
>|||Ok great.
Is there anything required to activate WOW on windows server or does it
automatically just work when you install the Workgroup Edition?
Also can you just confirm that the following scenario is doable:
Two SQL machines with copy of SQL 2005 Standard Edition
named SQL1 and SQL2 (both with there own separate internal ip address)
SQL1 has two databases called DB1 and DB2
SQL2 has two databases called DB3 and DB4
Spare Server (SPARE1) with copy of SQL 2005 Standard Edition for the Mirror
Witness Server (WIT1)
DB1,DB2,DB3,DB4 are mirrored to the Spare Server (SPARE1) with WIT1 as the
Witness Server
Now if both SQL1 and SQ2 fail at the same time can the Mirror take over all
the connections to these servers?
Thanks.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23DS1h9jGGHA.3320@.TK2MSFTNGP12.phx.gbl...
> Most of the benefits of 64 bit architectures are a result of the flat
> memory space but Workgroup Edition is not going to be able to take
> advantage of most of that. running a 32 bit edition in WOW allows 4 GB of
> user space so there is some advantage there. Currently, 64 bit processors
> are generally slower than the fastest 32 bit processors so in some cases a
> 32 bit processor might actually give better performance than a 64 bit
> processor and WOW. Of course, with a 64 bit machine you have the
> advantage of being able to upgrade to Standard edition and take advantage
> of the flat memory space if you run out of horsepower in WOW.
> You can have multiple servers mirrored to a single DB Mirroring server
> because individual databases are mirrored. You would have to be careful
> to ensure that the mirror has enough resources to both handle the load of
> mirroring databases from several server and the load of running the
> databases when they're failed over.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "greg" <greg_platt@.hotmail.com> wrote in message
> news:uBwm4ejGGHA.3916@.TK2MSFTNGP10.phx.gbl...
>> Thanks David,
>> So for 1) i'm not sure you've answered the question. I know Workgroup
>> Edition is 32bit but it can run on Windows 2003 Standard 64bit edition
>> using WOW. Now because i have a 64bit Opteron will i see SQL run quicker
>> in this config as opposed to using Windows 2003 Standard 32bit Server?
>> Also are there any performance penalties using WOW?
>> For 3) i take it you mean you can only have one prinicipal server per
>> mirror?
>> So if i have two SQL server machines running different databases and i
>> need to use just 1 backup server incase one machine fails what are my
>> best options?
>> Log-Shipping? or Replication?
>> Clustering would be too expensive for us and Mirroring would also be too
>> expensive if you need one mirror for each SQL server machine.
>> Thanks.
>>
>> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
>> message news:%237r4ZseGGHA.1032@.TK2MSFTNGP15.phx.gbl...
>> "greg" <greg_platt@.hotmail.com> wrote in message
>> news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a few questions regarding sql server 2005 .
>> Hardware will be running with a single dual core 64 bit Opteron 175.
>> 1) Are there any performance advantages running sql 2005 Workgroup
>> Edition on Windows 2003 64 bit Edition? If so what are they?
>>
>> Yes. Workgroup Edition only comes in 32bit and can only use 3GB of RAM,
>> and lacks the tuning tools of SQL Server.
>>
>> 2) Are there any benchmarks on how much faster sql 2005 Standard
>> Edition vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit
>> Edition?
>> No. For small workloads there shouldn't be much difference.
>> 3) For sql 2005 Standard Edition and the database mirroring
>> functionality : is it possible to mirror multiple sql servers to just
>> one failover mirror or do you need a separate sql box to mirror each
>> one ?
>>
>> One mirror per database, although the mirror server can mirror multiple
>> databases.
>> David
>>
>|||WOW is always there. Any 32 bit software you install will run in the WOW.
Theoretically, your failover scenario will work if you keep in mind that the
mirror server will have to handle four databases in this case so unless this
server has significantly more power than the primary servers, performance
will suffer if you fail over all the databases.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"greg" <greg_platt@.hotmail.com> wrote in message
news:OmGebPlGGHA.3448@.TK2MSFTNGP10.phx.gbl...
> Ok great.
> Is there anything required to activate WOW on windows server or does it
> automatically just work when you install the Workgroup Edition?
> Also can you just confirm that the following scenario is doable:
> Two SQL machines with copy of SQL 2005 Standard Edition
> named SQL1 and SQL2 (both with there own separate internal ip address)
> SQL1 has two databases called DB1 and DB2
> SQL2 has two databases called DB3 and DB4
> Spare Server (SPARE1) with copy of SQL 2005 Standard Edition for the
> Mirror
> Witness Server (WIT1)
> DB1,DB2,DB3,DB4 are mirrored to the Spare Server (SPARE1) with WIT1 as the
> Witness Server
> Now if both SQL1 and SQ2 fail at the same time can the Mirror take over
> all the connections to these servers?
> Thanks.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:%23DS1h9jGGHA.3320@.TK2MSFTNGP12.phx.gbl...
>> Most of the benefits of 64 bit architectures are a result of the flat
>> memory space but Workgroup Edition is not going to be able to take
>> advantage of most of that. running a 32 bit edition in WOW allows 4 GB
>> of user space so there is some advantage there. Currently, 64 bit
>> processors are generally slower than the fastest 32 bit processors so in
>> some cases a 32 bit processor might actually give better performance than
>> a 64 bit processor and WOW. Of course, with a 64 bit machine you have
>> the advantage of being able to upgrade to Standard edition and take
>> advantage of the flat memory space if you run out of horsepower in WOW.
>> You can have multiple servers mirrored to a single DB Mirroring server
>> because individual databases are mirrored. You would have to be careful
>> to ensure that the mirror has enough resources to both handle the load of
>> mirroring databases from several server and the load of running the
>> databases when they're failed over.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "greg" <greg_platt@.hotmail.com> wrote in message
>> news:uBwm4ejGGHA.3916@.TK2MSFTNGP10.phx.gbl...
>> Thanks David,
>> So for 1) i'm not sure you've answered the question. I know Workgroup
>> Edition is 32bit but it can run on Windows 2003 Standard 64bit edition
>> using WOW. Now because i have a 64bit Opteron will i see SQL run quicker
>> in this config as opposed to using Windows 2003 Standard 32bit Server?
>> Also are there any performance penalties using WOW?
>> For 3) i take it you mean you can only have one prinicipal server per
>> mirror?
>> So if i have two SQL server machines running different databases and i
>> need to use just 1 backup server incase one machine fails what are my
>> best options?
>> Log-Shipping? or Replication?
>> Clustering would be too expensive for us and Mirroring would also be too
>> expensive if you need one mirror for each SQL server machine.
>> Thanks.
>>
>> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
>> message news:%237r4ZseGGHA.1032@.TK2MSFTNGP15.phx.gbl...
>> "greg" <greg_platt@.hotmail.com> wrote in message
>> news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
>> Hi,
>> I have a few questions regarding sql server 2005 .
>> Hardware will be running with a single dual core 64 bit Opteron 175.
>> 1) Are there any performance advantages running sql 2005 Workgroup
>> Edition on Windows 2003 64 bit Edition? If so what are they?
>>
>> Yes. Workgroup Edition only comes in 32bit and can only use 3GB of
>> RAM, and lacks the tuning tools of SQL Server.
>>
>> 2) Are there any benchmarks on how much faster sql 2005 Standard
>> Edition vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit
>> Edition?
>> No. For small workloads there shouldn't be much difference.
>> 3) For sql 2005 Standard Edition and the database mirroring
>> functionality : is it possible to mirror multiple sql servers to just
>> one failover mirror or do you need a separate sql box to mirror each
>> one ?
>>
>> One mirror per database, although the mirror server can mirror multiple
>> databases.
>> David
>>
>>
>|||1. Each principal can have exactly 1 mirror. A witness can service as many
principal/mirror pairs as you want it to. Mirroring occurs at a database
level, so you can have an instance of SQL Server where there are multiple
databases on that instance in the role of a mirror.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"greg" <greg_platt@.hotmail.com> wrote in message
news:%23Y7SECZGGHA.208@.tk2msftngp13.phx.gbl...
> Hi,
> I have a few questions regarding sql server 2005 .
> Hardware will be running with a single dual core 64 bit Opteron 175.
> 1) Are there any performance advantages running sql 2005 Workgroup Edition
> on Windows 2003 64 bit Edition? If so what are they?
> 2) Are there any benchmarks on how much faster sql 2005 Standard Edition
> vs sql 2005 Workgroup Edition runs on Windows 2003 64 bit Edition?
> 3) For sql 2005 Standard Edition and the database mirroring functionality
> : is it possible to mirror multiple sql servers to just one failover
> mirror or do you need a separate sql box to mirror each one ?
> Thanks
>

Mirroring + remoting

Hi,

I have a 3-tier app that is currently running on a simple single server setup. However, I have to adapt it to run on the following setup:

1) Client .NET app on client systems with remoting connection to...

2) Host .NET app with a DAL connecting to ...

3) SQL Server 2005 mirrored

Using mirroring, if the principle SQL server goes down it switches automatically to the mirror server.

My question relates to my connections. What do I need to do to make sure the Client and Host apps follow SQL?

There are two setups I have in mind:

1) Host app + SQL on same box

2) Host app on its own server + SQL on its server (+mirror)

With these scenarios:

Setup 1 - SQL fails but server continues - Host app has to connect to mirror - clients continue to connect to Host on principle server.

Setup 1 - Whole server fails - Host on mirror server connects to mirror SQL and clints now have to locate Host on mirror.

Setup 2 - SQL's server fails so mirror switches in. Only Host app has to re-direct. Clients connect to same Host app.

This is new to me, so if anyone can advise, or direct me to the right info.

Hi,

I assume your solution employs the Presentation Layer <-> Business Layer <-> Data Layer architecture. Since you want to maximise transparency to the client application (pres layer), in my opinion, it's better to go with option 2 and put the host app on a separate server from the database to decrease the probability of multiple failures (if the machine with host + sql goes down - both will be inaccessible).

If you do this and code the host app to use ADO.NET to connect to the database, you could take advantage of the ability of the SqlConnection object to automatically re-connect to the failover partner in a mirrored configuration. This MSDN article explains how this works - http://msdn2.microsoft.com/en-us/library/5h52hef8.aspx.

In addition, if you want complete transparency to the client application, you will still have to make it handle the case where the host fails.

-- Kaloian.

|||

Thanks Kaloian,

That leaves me with the problem of having the clinet apps fail over to another server when the host app's server fails. I guess I'm asking is there a remoting option to fail over, similar to the Failover Partner attribute in the sql connection string? Or am I going to have to trap the failure and code the switch?

|||

As far as I know there's no such mechanism, but you may want to post this question to the .NET Remoting newsgroup - http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=41&SiteID=1

- Kaloian.

Mirroring + remoting

Hi,

I have a 3-tier app that is currently running on a simple single server setup. However, I have to adapt it to run on the following setup:

1) Client .NET app on client systems with remoting connection to...

2) Host .NET app with a DAL connecting to ...

3) SQL Server 2005 mirrored

Using mirroring, if the principle SQL server goes down it switches automatically to the mirror server.

My question relates to my connections. What do I need to do to make sure the Client and Host apps follow SQL?

There are two setups I have in mind:

1) Host app + SQL on same box

2) Host app on its own server + SQL on its server (+mirror)

With these scenarios:

Setup 1 - SQL fails but server continues - Host app has to connect to mirror - clients continue to connect to Host on principle server.

Setup 1 - Whole server fails - Host on mirror server connects to mirror SQL and clints now have to locate Host on mirror.

Setup 2 - SQL's server fails so mirror switches in. Only Host app has to re-direct. Clients connect to same Host app.

This is new to me, so if anyone can advise, or direct me to the right info.

Hi,

In addition, if you want complete transparency to the client application, you will still have to make it handle the case where the host fails.

-- Kaloian.

|||

Thanks Kaloian,

|||

As far as I know there's no such mechanism, but you may want to post this question to the .NET Remoting newsgroup - http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=41&SiteID=1

- Kaloian.

Wednesday, March 28, 2012

Mirroring

We are moving our asp application from SQL2k to SQL2k5. I implemented
database mirroring for my critical databases, which is setup & running. I
modified the connection string in the Global.asa to point to my new servers.
When both SQL servers are up & running I connect to the primary database.
However, when the server hosting the primary database is stopped, I get an
error regarding the connection string.
Is this an application error that needs to be resolved? What do I tell the
developers to do?
Is this a problem with the SQL connection string? Does anyone have working
examples?
Also, I am using a witness server.
Does anyone have any test procedures/scripts/scenarios to insure mirroring
is working as it should. I thought I could stop SQL on a server run a test,
restart SQL & then check the databases.
I'm ok at server & database admin but poor at database programming. And
brand new to SQL2k5 mirroring.
Thanks"BigSam" <BigSam@.discussions.microsoft.com> wrote in message
news:26E0585C-23F3-4C84-B466-B8EFB44504B4@.microsoft.com...
> We are moving our asp application from SQL2k to SQL2k5. I implemented
> database mirroring for my critical databases, which is setup & running. I
> modified the connection string in the Global.asa to point to my new
> servers.
> When both SQL servers are up & running I connect to the primary database.
> However, when the server hosting the primary database is stopped, I get an
> error regarding the connection string.
> Is this an application error that needs to be resolved? What do I tell the
> developers to do?
> Is this a problem with the SQL connection string? Does anyone have working
> examples?
> Also, I am using a witness server.
> Does anyone have any test procedures/scripts/scenarios to insure mirroring
> is working as it should. I thought I could stop SQL on a server run a
> test,
> restart SQL & then check the databases.
> I'm ok at server & database admin but poor at database programming. And
> brand new to SQL2k5 mirroring.
>
Does your connection string specify both the principal and the mirror? If
not, failover will work, but startup when the principal is down will not.
See:
System.Data.SqlConnection.ConnectionString Property
Failover Partner
N/A
The name of the failover partner server where database mirroring is
configured.
The Failover Partner keyword is not supported by .NET Framework version 1.0
or 1.1.
http://msdn2.microsoft.com/en-us/li...tionstring.aspx
David|||"David Browne" wrote:

>
> "BigSam" <BigSam@.discussions.microsoft.com> wrote in message
> news:26E0585C-23F3-4C84-B466-B8EFB44504B4@.microsoft.com...
> Does your connection string specify both the principal and the mirror? If
> not, failover will work, but startup when the principal is down will not.
> See:
> System.Data.SqlConnection.ConnectionString Property
> Failover Partner
> N/A
> The name of the failover partner server where database mirroring is
> configured.
> The Failover Partner keyword is not supported by .NET Framework version 1.
0
> or 1.1.
> http://msdn2.microsoft.com/en-us/li...tionstring.aspx
>
> David
> This is the connection string set in the Global.asa:
Application("ConnectionString") = "Provider=sqloledb;Server=SQL1;Failover
Partner=SQL2;Initial Catalog=MainDB;UID=TestUser;Pwd=Test99"
Also, we're not using asp.net - just plain old ASP.|||"BigSam" <BigSam@.discussions.microsoft.com> wrote in message
news:E89D67CA-4BA6-4A87-B053-F3F10BC1D3AC@.microsoft.com...
>
> "David Browne" wrote:
>
> Application("ConnectionString") = "Provider=sqloledb;Server=SQL1;Failover
> Partner=SQL2;Initial Catalog=MainDB;UID=TestUser;Pwd=Test99"
> Also, we're not using asp.net - just plain old ASP.
>
The OleDb provider you're using isn't mirroring-aware. The SQLNCLI the new
SqlServer Native Client provider, if it works correctly with your
application. See:
Using ADO with SQL Native Client
http://msdn2.microsoft.com/en-us/library/ms130978.aspx
If you stick with SQLOLEDB, then you can use DNS or BigIP to manually switch
the traffic between servers, or just change your config and boune the site.
David|||Thanks for your reply.
Yesterday & was able to determine that without mirroring I could connect to
each server with the SQL login. However, with mirroring enabled I could only
connect to SQL1 with the SQL login. I began to suspect the SID & found this
article: http://support.microsoft.com/default.aspx/kb/918992/
"Magas" wrote:
[vbcol=seagreen]
> If you use SQL Server login to connect to the mirror database - make sure
> logins on both mirror servers have the same SID. The easiest way to do it
-
> copy login from one server to another using SSIS package.
>
> "BigSam" wrote:
>

Mirroring

Is there a way to detect if the principal or mirror is running the database?
I want build my own altert system, sending an SMS whenever a automatic
failover/failback happens.
Per Schjetne"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
You can set alerts on the messages in the event log. Talk to your monitoring
application vendor for more info.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||select * from sys.database_mirroring
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>|||The sys.dm_database_mirroring view will give you the state information that
you
need to monitor. You will need to access this on both partners.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>

Mirroring

We are moving our asp application from SQL2k to SQL2k5. I implemented
database mirroring for my critical databases, which is setup & running. I
modified the connection string in the Global.asa to point to my new servers.
When both SQL servers are up & running I connect to the primary database.
However, when the server hosting the primary database is stopped, I get an
error regarding the connection string.
Is this an application error that needs to be resolved? What do I tell the
developers to do?
Is this a problem with the SQL connection string? Does anyone have working
examples?
Also, I am using a witness server.
Does anyone have any test procedures/scripts/scenarios to insure mirroring
is working as it should. I thought I could stop SQL on a server run a test,
restart SQL & then check the databases.
I'm ok at server & database admin but poor at database programming. And
brand new to SQL2k5 mirroring.
Thanks
"BigSam" <BigSam@.discussions.microsoft.com> wrote in message
news:26E0585C-23F3-4C84-B466-B8EFB44504B4@.microsoft.com...
> We are moving our asp application from SQL2k to SQL2k5. I implemented
> database mirroring for my critical databases, which is setup & running. I
> modified the connection string in the Global.asa to point to my new
> servers.
> When both SQL servers are up & running I connect to the primary database.
> However, when the server hosting the primary database is stopped, I get an
> error regarding the connection string.
> Is this an application error that needs to be resolved? What do I tell the
> developers to do?
> Is this a problem with the SQL connection string? Does anyone have working
> examples?
> Also, I am using a witness server.
> Does anyone have any test procedures/scripts/scenarios to insure mirroring
> is working as it should. I thought I could stop SQL on a server run a
> test,
> restart SQL & then check the databases.
> I'm ok at server & database admin but poor at database programming. And
> brand new to SQL2k5 mirroring.
>
Does your connection string specify both the principal and the mirror? If
not, failover will work, but startup when the principal is down will not.
See:
System.Data.SqlConnection.ConnectionString Property
Failover Partner
N/A
The name of the failover partner server where database mirroring is
configured.
The Failover Partner keyword is not supported by .NET Framework version 1.0
or 1.1.
[url]http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstri ng.aspx[/url]
David
|||"David Browne" wrote:

>
> "BigSam" <BigSam@.discussions.microsoft.com> wrote in message
> news:26E0585C-23F3-4C84-B466-B8EFB44504B4@.microsoft.com...
> Does your connection string specify both the principal and the mirror? If
> not, failover will work, but startup when the principal is down will not.
> See:
> System.Data.SqlConnection.ConnectionString Property
> Failover Partner
> N/A
> The name of the failover partner server where database mirroring is
> configured.
> The Failover Partner keyword is not supported by .NET Framework version 1.0
> or 1.1.
> [url]http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstri ng.aspx[/url]
>
> David
> This is the connection string set in the Global.asa:
Application("ConnectionString") = "Provider=sqloledb;Server=SQL1;Failover
Partner=SQL2;Initial Catalog=MainDB;UID=TestUser;Pwd=Test99"
Also, we're not using asp.net - just plain old ASP.
|||"BigSam" <BigSam@.discussions.microsoft.com> wrote in message
news:E89D67CA-4BA6-4A87-B053-F3F10BC1D3AC@.microsoft.com...
>
> "David Browne" wrote:
> Application("ConnectionString") = "Provider=sqloledb;Server=SQL1;Failover
> Partner=SQL2;Initial Catalog=MainDB;UID=TestUser;Pwd=Test99"
> Also, we're not using asp.net - just plain old ASP.
>
The OleDb provider you're using isn't mirroring-aware. The SQLNCLI the new
SqlServer Native Client provider, if it works correctly with your
application. See:
Using ADO with SQL Native Client
http://msdn2.microsoft.com/en-us/library/ms130978.aspx
If you stick with SQLOLEDB, then you can use DNS or BigIP to manually switch
the traffic between servers, or just change your config and boune the site.
David
|||Thanks for your reply.
Yesterday & was able to determine that without mirroring I could connect to
each server with the SQL login. However, with mirroring enabled I could only
connect to SQL1 with the SQL login. I began to suspect the SID & found this
article: http://support.microsoft.com/default.aspx/kb/918992/
"Magas" wrote:
[vbcol=seagreen]
> If you use SQL Server login to connect to the mirror database - make sure
> logins on both mirror servers have the same SID. The easiest way to do it -
> copy login from one server to another using SSIS package.
>
> "BigSam" wrote:
sql

Mirroring

Is there a way to detect if the principal or mirror is running the database?
I want build my own altert system, sending an SMS whenever a automatic
failover/failback happens.
Per Schjetne"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
You can set alerts on the messages in the event log. Talk to your monitoring
application vendor for more info.
--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp|||select * from sys.database_mirroring
--
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>|||The sys.dm_database_mirroring view will give you the state information that
you
need to monitor. You will need to access this on both partners.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Per Schjetne" <newsuser1@.gdconsult.no> wrote in message
news:%23V%23sM6caGHA.1196@.TK2MSFTNGP03.phx.gbl...
> Is there a way to detect if the principal or mirror is running the
> database? I want build my own altert system, sending an SMS whenever a
> automatic failover/failback happens.
> Per Schjetne
>

Friday, March 23, 2012

Minimum version of Visual Studio.NET

What is the minimum requirement or version of Visual Studio.NET
necessary for editing reports when running Reporting Services. I am
running on a SQL 2000 sp3 and Windows 2003 server.Anything that comes with VS.2003 (It cannot be VS 2005). The cheapest is
VB.Net
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1140804364.362272.141300@.z34g2000cwc.googlegroups.com...
> What is the minimum requirement or version of Visual Studio.NET
> necessary for editing reports when running Reporting Services. I am
> running on a SQL 2000 sp3 and Windows 2003 server.
>|||Thanks, I will try that :-)
/Ren=E9

Minimum Setup Requirements for SQL 2005 Replication.

What are the minimum setup requirements to support the following.
2 Remote Laptops running SQL Server 2005 Express databases with the ability
to synchronize with each other. Also they should be able to synch with a
server hosting a SQL Database whci is accessible from 2 other Desktop PCs.
What are the SQL CAL Licensing issues that would apply to this scenario.
Regards
Unfortunately SQL Server Express can only be a subscriber to all types of
replication. All subscriptions must be created through RMO or replication
stored procedures.
Regarding your desktop pc's - If they are running workgroup edition they can
have up to 25 merge subscribers, but 5 transactional subscribers. In regards
to licensing anything which accesses the desktop must have a license, which
can be a CAL or a server per processor license (which will not make a whole
lot of sense).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Stuart Lowe" <StuartLowe@.discussions.microsoft.com> wrote in message
news:6C1471E6-61F1-4BF2-AAA8-16E67A29A967@.microsoft.com...
> What are the minimum setup requirements to support the following.
> 2 Remote Laptops running SQL Server 2005 Express databases with the
> ability
> to synchronize with each other. Also they should be able to synch with a
> server hosting a SQL Database whci is accessible from 2 other Desktop PCs.
> What are the SQL CAL Licensing issues that would apply to this scenario.
> Regards
sql

Minimum RAM Requirement For installation

256 RAM is running on my computer. is it possible to run Microsoft SQL Server 2005 Reporting Services on it?

NOTE: I installed Microsoft SQL Server 2005 Reporting Services. By the installation, it gives an error, that system resource is not enough. Although this, installation resume, but program not worked at the end.

No.

http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en#Requirements

Friday, March 9, 2012

Migration of DB2 data to SQL 2005

Hello,

What is the best option for migration of DB2 data to SQL 2005?

DB2 is running on AIX.

Thanks,

Herman

You should investigate using the DB2 driver available in the SQL Server Feature Pack.

http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2-A67D-48053B8F9FAD/DB2OLEDB.exe

Donald

Wednesday, March 7, 2012

Migration from SQL7 to SQL2000

Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to move my databases over to a SQL 2000 Windows 2003 server. What is the best method. These are two different boxes. Any help is greatly appreciated.
Scott KeeganHave a look here:
http://msdn.microsoft.com/SQL/sqlmigratingdata/default.aspx
--
Andrew J. Kelly SQL MVP
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Scott
Install SQL Server on Widows 2003 and perfom RESTORE all users databases.
It might be a collation conflict but since SQL Server 2000 you can change it
even per column.
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Hi,
Migration from SQl 7 to SQl 2000 is straight forward, you can BACKUP and
RESTORE or use
sp_detach_db and sp_attach_db.
You could also probably also use the upgrade wizard .
Look into the below KB articles related to migration:
move the data via backup and restore
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304692
sp_detach_db and sp_attach_db
http://support.microsoft.com/support/kb/articles/q224/0/71.asp
one more option -- the copy database wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
PRB: User Logon and/or Permission Errors After Restoring Dump (Q168001)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168001
Thanks
Hari
MCDBA
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Is there a priority order on a where clause? Or does SQL check all of the
where clause conditions all of the time? I have a case where I can,
sometimes, hit non-numeric data in a column (caused by some bad
conversions). Right now we have the following where clause:
WHERE convert(integer, ?) BETWEEN convert(integer, low_street_num) AND
convert(integer, high_street_num)
AND (street_name = ? OR street_alias_name = ?)
AND city = ?
AND state_cd = ?
AND zip_cd LIKE ?
AND (juris_cd = ? OR juris_cd IS NULL)
AND (side = ? OR side = 'B')
AND status_cd = 'A'
AND (side = ? OR side = 'B')
AND status_cd = 'A'
I am wondering if we were to change to put the status_cd = 'A' first would
the query skip all entries whose status_cd is not 'A' and not even try to do
the convert(integer) statement at all? Or is it going to try to do the
convert(integer) regardless and my only solution is to make some routine to
fix the non-numeric data or adjust this sql to ensure the data is numeric
before trying to do the convert?
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.com|||You cannot trust SQL Server to not hit the bad rows. Not even by pushing the filter inside a derived
table. I've been there. Put the stuff in a temp table and work against that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ed Fultz" <efultz@.yahoo.com> wrote in message news:O6blHRSWEHA.4056@.TK2MSFTNGP11.phx.gbl...
> Is there a priority order on a where clause? Or does SQL check all of the
> where clause conditions all of the time? I have a case where I can,
> sometimes, hit non-numeric data in a column (caused by some bad
> conversions). Right now we have the following where clause:
> WHERE convert(integer, ?) BETWEEN convert(integer, low_street_num) AND
> convert(integer, high_street_num)
> AND (street_name = ? OR street_alias_name = ?)
> AND city = ?
> AND state_cd = ?
> AND zip_cd LIKE ?
> AND (juris_cd = ? OR juris_cd IS NULL)
> AND (side = ? OR side = 'B')
> AND status_cd = 'A'
> AND (side = ? OR side = 'B')
> AND status_cd = 'A'
> I am wondering if we were to change to put the status_cd = 'A' first would
> the query skip all entries whose status_cd is not 'A' and not even try to do
> the convert(integer) statement at all? Or is it going to try to do the
> convert(integer) regardless and my only solution is to make some routine to
> fix the non-numeric data or adjust this sql to ensure the data is numeric
> before trying to do the convert?
>
> --
> Edward Fultz
> Sr. Software Engineer
> Pamet Systems
> Acton, Ma
> www.pametsystems.com
>|||You should be careful to test such a migration thoroughly:
We had a system running on MSSQL7 (MSDE) that we migrated
to MSSQL2000 Ent.Ed.
Restore finished fine, program seemded to run, but after
some days it crashed. Then nothing and then again. We
found out the following:
We built up SQL statements so string values were given as
char(65)+char(66)+...
Now, this sometimes produced queries as big as 8-9kB,
which MSSQL7 handled fine.
MSSQL2000, however, gave sql parse error. This shouldn't
be a problem until the length of the query reaches ~100kB.
Local Microsoft wanted to make this work badly, but
couldn't do it. We had to backtrack to MSSQL7.
>--Original Message--
>Hi, here is my delema, I have SQL 7 running on a NT4 box
and I want to move my databases over to a SQL 2000 Windows
2003 server. What is the best method. These are two
different boxes. Any help is greatly appreciated.
>Scott Keegan
>.
>

Saturday, February 25, 2012

Migration from MS Access 2003

Hello,

I'm very new to MS SQL Server; I just downloaded Express 2005 yesterday. I have it up and running; it seems to be working fine.

Now onto business - I need to migrate data from existing MS Access 2003. How, exactly, do I do this? I've tried searching MSDN, TechNet, and here, and while I get results that seem to tell part of the story, I don't seem to get a true "How to" for this task.

Can someone please assist me with this?

Thank you.

Here you go:

http://support.microsoft.com/default.aspx/kb/237980

Buck Woody

Migration from MS Access 2003

Hello,

I'm very new to MS SQL Server; I just downloaded Express 2005 yesterday. I have it up and running; it seems to be working fine.

Can someone please assist me with this?

Thank you.

Here you go:

http://support.microsoft.com/default.aspx/kb/237980

Buck Woody

Migration Access - Sql Server

Hi,
I am new to Sql Server.
I have a development done in MS Access, it is running on a server, splitted BE / FE and replications for we have 5 laptops that run and update the DB offline and then sync to the LAN, when they return to headquaters.
I want to migrate this to them syncing through the internet to a main BE, but I still want them to have an offline version for them to work during the day.
Can this me done in Sql Server? Can I easily re-use my Access development ?
The BE would be in a 3rds party ISP, what would my requirements be?
Cheers
Pata.
Pata,
to be honest I haven't seen the acronyms BE or FE before, but the main
principle is straightforward enough.
You could upgrade all your access instances entirely to SQL Server or you
could use heterogenous replication and have a central publisher at HO which
is SQL Server with remote subscribers which are access. Either way, we are
talking about merge replication, with pull subscriptions. As this is an
internet project, you might find this link useful:
http://support.microsoft.com/?id=321822.
Please can you post back with the BE/FE descriptions and I might then expand
on things a bit.
HTH,
Paul Ibison

Migration ?

Hello,
I currently have a SQL 2000 SP3 STD running in my org, I want to move it's
contents to a clustered (two node) system running SQL 2005 STD edition. Is
it possible to move the entire contents of my old SQL environment to the new
environment? I would like to preserve user logins and the current instance
name of my old server. I know it might require me renaming the old SQL
server name when I get to that point. If someone could give me some tips on
how (or if it's even possible) to do this I would be highly greatful.
Thank you
Alex Anderson
You have to move the databases to the new server individually. Most of
these were written for 2000 but still apply to 2005.
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/featu...le.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/colu...rdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scri...tions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
news:2DF0B36D-5B38-4BE1-A448-91CE4F33F5B2@.microsoft.com...
> Hello,
> I currently have a SQL 2000 SP3 STD running in my org, I want to move it's
> contents to a clustered (two node) system running SQL 2005 STD edition.
> Is
> it possible to move the entire contents of my old SQL environment to the
> new
> environment? I would like to preserve user logins and the current
> instance
> name of my old server. I know it might require me renaming the old SQL
> server name when I get to that point. If someone could give me some tips
> on
> how (or if it's even possible) to do this I would be highly greatful.
> Thank you
> Alex Anderson
>
|||Actually, it can be done a bit more simply than that. You need to do the
following:
1. Configure the cluster
2. Install a SQL Server failover cluster instance
3. Backup the master database on your standalone and restore it to the
failover cluster instance
4. Backup msdb and restore it to the failover cluster instance
5. Move your databases using either a detach/attach or backup/restore
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:et0zGJSVGHA.6084@.TK2MSFTNGP14.phx.gbl...
> You have to move the databases to the new server individually. Most of
> these were written for 2000 but still apply to 2005.
> http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
> http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx
> Moving system dbs 2005
> http://www.databasejournal.com/featu...le.php/3379901
> Moving system DB's 2000
> http://www.support.microsoft.com/?id=314546 Moving DB's between
> Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server
> Databases to a New Location with Detach/Attach
> http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a
> Restore
> http://www.sqlservercentral.com/colu...rdatabases.asp
> Moving Users
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs
> after a Restore
> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or
> Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scri...p?scriptid=599
> Restoring a .mdf
> http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
> for SQL Server
> http://www.support.microsoft.com/?id=320125 Moving a Diagram
> http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
> http://www.sqlservercentral.com/scri...tions/1598.asp Script
> Roles and Permissions
> --
> Andrew J. Kelly SQL MVP
>
> "Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
> news:2DF0B36D-5B38-4BE1-A448-91CE4F33F5B2@.microsoft.com...
>
|||Michael,
Moving the Master and MSDB database, what if the old server where those
databases are coming from are different builds? Will a restore on the SQL
2005 cluster allow this?
Thank you
Alex Anderson
"Michael Hotek" wrote:

> Actually, it can be done a bit more simply than that. You need to do the
> following:
> 1. Configure the cluster
> 2. Install a SQL Server failover cluster instance
> 3. Backup the master database on your standalone and restore it to the
> failover cluster instance
> 4. Backup msdb and restore it to the failover cluster instance
> 5. Move your databases using either a detach/attach or backup/restore
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:et0zGJSVGHA.6084@.TK2MSFTNGP14.phx.gbl...
>
>
|||During a restore, all of the metadata is upgraded. So, yes, it does work.
You will obviously want to test it before doing it in production.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
news:0A3A75CF-166A-4BD7-88C9-1B55B519B9B7@.microsoft.com...[vbcol=seagreen]
> Michael,
> Moving the Master and MSDB database, what if the old server where those
> databases are coming from are different builds? Will a restore on the SQL
> 2005 cluster allow this?
> Thank you
> Alex Anderson
>
> "Michael Hotek" wrote:
|||Michael,
I've tried every way I can think of trying to restore the master database.
I fail every time because it's complaining about the build numbers being
different. Is there something I can need to check to override this?
Thank you
Alex Anderson
"Michael Hotek" wrote:

> During a restore, all of the metadata is upgraded. So, yes, it does work.
> You will obviously want to test it before doing it in production.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Alex Anderson" <AlexAnderson@.discussions.microsoft.com> wrote in message
> news:0A3A75CF-166A-4BD7-88C9-1B55B519B9B7@.microsoft.com...
>
>

Friday, March 30, 2012

Mirroring and 64 vs 32 bit performance

Mirroring and 64 vs 32 bit performance

Mirroring and 64 vs 32 bit performance

Mirroring + remoting

Mirroring + remoting

Wednesday, March 28, 2012

Mirroring

Mirroring

Mirroring

Mirroring

Friday, March 23, 2012

Minimum version of Visual Studio.NET

Minimum Setup Requirements for SQL 2005 Replication.

Minimum RAM Requirement For installation

Friday, March 9, 2012

Migration of DB2 data to SQL 2005

Wednesday, March 7, 2012

Migration from SQL7 to SQL2000

Migration from SQL7 to SQL2000

Migration from SQL7 to SQL2000

Saturday, February 25, 2012

Migration from MS Access 2003

Migration from MS Access 2003

Migration Access - Sql Server

Migration ?

Migrating to SQL 2005

Blog Archive

About Me