Upgrade MS SQL 2005 to MS SQL 2008 (R2) for High-Availability SAP ERP System

Hi,
We are having ECC 6.0 SR3 Hight-Availability system on windows cluster environment.
Our platform is Windows Server 2008 SR2 with MS SQL Server 2005 SR3. We have two nodes in our windows cluster. Active-passive nodes.
Node-1 is having CI, ASCS, ERS & DATABASE
Node-2 is having DI, ERS & stand-by database software.
I've check all the pre-requisites for sql upgrade.
our kernel is on 700_Rel. I'm planning to stabilize the kernel with 721_Rel before Database upgrade.
Support package patch level condition is met for sql upgrade in our scenario.
Now we are planning to upgrade our MS SQL Server from 2005 sr3 to MS SQL Server 2008r2.
Please provide me the steps for Kernel upgrade and sql upgrade to 2008r2 on Windows cluster environment.
Thanks
Venkat

Hi Venkat
1. Could you share your ECC support package level & also you can check the PAM
2. Yes you can upgrade the MS Sql to 2008 R2, before starting upgrade Kindly ensure the full OS / DB level backup on both cluster node's
3. MS Sql 2008 R2 upgrade refer the SAP Note
1152240 - Setting Up Microsoft SQL Server 2008 (R2)
4. For Kernel upgrade its release change kindly go thru the SAP Notes
1713986 - Installation of kernel 721 (EXT)
1728283 - SAP Kernel 721: General Information
1726899 - 721 DCK: Upgrade from 7.0n to 7.1n
BR
SS

Similar Messages

SQL query is slow after upgrading from SQL 2008 to SQL 2008 R2

Hello
We were using SQL 2008 Standard, but after upgrading to R2, following query is much slower (takes 5 seconds instead of less than 1 second), how is this possible?
Regards, Hennie
SELECT
P.BSN,
P.Persnr,
P.Roepnaam,
P.Tussenvoegsels,
P.Achternaam,
P.Geslacht,
COALESCE (P.Achternaam + ', ' + P.Roepnaam + ' ' + P.Tussenvoegsels, P.Achternaam + ', ' + P.Roepnaam, P.Achternaam) AS naamvolledig,
P.Telmobiel,
P.Telvast,
P.Postcode,
G.groep,
COALESCE (RM.nieuweDag, GR.Dag) AS dag,
COALESCE (RM.nieuweDatum, GR.datum) AS datum,
DATEPART(ww, COALESCE (RM.nieuweDatum, GR.datum)) AS weeknummer,
DATEPART(yyyy, COALESCE (RM.nieuweDatum, GR.datum)) AS jaar,
CONVERT(VARCHAR(8),
  CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweBegintijd,
   CASE WHEN GR.Tijdspan = 2 THEN R.begintijd2 ELSE R.begintijd END)
  ELSE COALESCE (RM.nieuweBegintijd, GR.begintijd) END, 108) AS begintijdberekend,
CONVERT(VARCHAR(8),
  CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweEindtijd,
   CASE WHEN GR.Tijdspan = 2 THEN R.eindtijd2 ELSE R.eindtijd END)
  ELSE COALESCE (RM.nieuweEindtijd, GR.eindtijd) END, 108) AS eindtijdberekend,
CASE WHEN GR.ID_lokaties = 3 THEN
   CONVERT(NCHAR(5), COALESCE (RM.nieuweBegintijd,CASE WHEN GR.Tijdspan = 2 THEN R.begintijd2 ELSE R.begintijd END), 108) + '-' +
   CONVERT(NCHAR(5), COALESCE (RM.nieuweEindtijd, CASE WHEN GR.Tijdspan = 2 THEN R.eindtijd2 ELSE R.eindtijd END), 108)
  ELSE CONVERT(NCHAR(5),COALESCE (RM.nieuweBegintijd, GR.begintijd), 108) + '-' + CONVERT(NCHAR(5), COALESCE (RM.nieuweEindtijd, GR.eindtijd), 108)
  END AS Tijdspanne,
CASE
  WHEN GR.ID_lokaties = 3 AND R.id_relaties = 9 THEN 'Werk Intern'
  WHEN GR.ID_lokaties = 3 THEN R.relatienaam
  ELSE L.lokatie END AS Lokatieberekend,
R.relatienaam AS relatie,
L.IntExt,
RA.Omschrijving AS roosteractiviteit,
A.instroomdatum,
A.uitstroomdatum,
TT.trajecttype,
W.Naamvolledig AS Werkcoach,
A.ID_groepen,
T.ID_personen,
A.ID_werkcoaches,
CASE
  WHEN GR.ID_lokaties = 3 AND R.id_relaties = 9 THEN 20
  WHEN GR.ID_lokaties = 3 THEN R.id_relaties
  ELSE L.ID_relaties END AS ID_lokatieberekend,
A.ID_relaties AS ID_relatie,
R.nummer2 AS capaciteit,
GR.ID_groepsroosters,
CAST(CASE WHEN foto IS NOT NULL THEN 'Ja' ELSE NULL END AS char(2)) AS Foto,
W.Email,
W.TelefoonMobiel,
W.TelefoonVast
FROM
dbo.personen AS P INNER JOIN
dbo.trajecten AS T ON T.ID_personen = P.ID_personen INNER JOIN
dbo.trajecttype AS TT ON T.ID_trajecttype = TT.ID_trajecttype INNER JOIN
dbo.trajectactiviteiten AS A ON A.ID_trajecten = T.ID_trajecten INNER JOIN
dbo.groepsroosters AS GR ON GR.ID_groepen = A.ID_groepen LEFT OUTER JOIN
dbo.roosteractiviteit AS RA ON GR.ID_roosteractiviteit = RA.ID_roosteractiviteit INNER JOIN
dbo.lokaties AS L ON GR.ID_lokaties = L.ID_lokaties INNER JOIN
dbo.werkcoaches AS W ON A.ID_werkcoaches = W.ID_werkcoaches INNER JOIN
dbo.groepen AS G ON A.ID_groepen = G.ID_groepen LEFT OUTER JOIN
dbo.relaties AS R ON A.ID_relaties = R.ID_relaties LEFT OUTER JOIN
dbo.roostermutaties AS RM ON P.ID_personen = RM.ID_personen AND GR.ID_groepsroosters = RM.ID_groepsroosters AND RM.aanwezig IS NULL
WHERE
(COALESCE (RM.nieuweDatum, GR.datum) BETWEEN GETDATE() - 1 AND GETDATE() + 13)
AND (COALESCE (DATEDIFF(day, COALESCE (RM.nieuweDatum, GR.datum), A.uitstroomdatum), 0) >= 0)
AND (DATEDIFF(day, A.instroomdatum, COALESCE (RM.nieuweDatum, GR.datum)) >= 0)
AND ((SELECT COUNT(*) AS Expr1
  FROM dbo.roostermutaties AS RM2
  WHERE (P.ID_personen = ID_personen)
  AND (GR.ID_groepsroosters = ID_groepsroosters)
  AND (CONVERT(VARCHAR(8), begintijdafwezig, 108) = CONVERT(VARCHAR(8),
  CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweBegintijd,
  CASE WHEN GR.Tijdspan = 2 THEN R.begintijd2 ELSE R.begintijd END)
  ELSE COALESCE (RM.nieuweBegintijd, GR.begintijd) END, 108)) AND
  (CONVERT(VARCHAR(8), eindtijdafwezig, 108) = CONVERT(VARCHAR(8), CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweEindtijd,
  CASE WHEN GR.Tijdspan = 2 THEN R.eindtijd2 ELSE R.eindtijd END) ELSE COALESCE (RM.nieuweEindtijd, GR.eindtijd) END, 108))) = 0)

We were using SQL 2008 Standard, but after upgrading to R2, following query is much slower (takes 5 seconds instead of less than 1 second), how is this possible?
It is not uncommon to experience performance problems following an upgrade when there are issues with original query. Non-sargable expressions like Olaf called out are often the culprit, as well as lack of useful indexes and statistics.
The optimizer cannot glean accurate row count estimates or use indexes efficiently so the resultant plan may not be optimal for the task at hand. It is only by happenstance that old plan performed better; it could just as well be the other way around,
but again only by chance since the optimizer is guessing.
You might also try using EXISTS instead of SELECT COUNT(*)...= 0:
AND EXISTS(SELECT *
FROM dbo.roostermutaties AS RM2
WHERE P.ID_personen = ID_personen
AND GR.ID_groepsroosters = ID_groepsroosters
AND CONVERT(VARCHAR(8), begintijdafwezig, 108) = CONVERT(VARCHAR(8),
CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweBegintijd,
CASE WHEN GR.Tijdspan = 2 THEN R.begintijd2 ELSE R.begintijd END)
ELSE COALESCE (RM.nieuweBegintijd, GR.begintijd) END, 108)
AND CONVERT(VARCHAR(8), eindtijdafwezig, 108) = CONVERT(VARCHAR(8), CASE WHEN GR.ID_lokaties = 3 THEN COALESCE (RM.nieuweEindtijd,
CASE WHEN GR.Tijdspan = 2 THEN R.eindtijd2 ELSE R.eindtijd END) ELSE COALESCE (RM.nieuweEindtijd, GR.eindtijd) END, 108))
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Steps to upgrade from sql 2008 r2 se (nonclustered) to sql 2012 se (clustered)

hello,
I am currently running a non clustered instance of a sqlserver 2008 R2 SE and need to upgrade to a clustered instance of SQLServer 2012 SE. The underlying OS is Windows 2008 R2 SE. I already bought the second server with the same os online but havent installed
sql 2012 yet.
I am thinking of backing up my databases and script out all the logins and linked servers first.
Then upgrade the SQLServer 2008 R2 SE to 2012 SE. But can I upgrade it to a clustered instance directly? If yes then I can definitely add the other server to the cluster while installing sql.
Can someone point me to the right steps for this upgrade process
Thanks

Hello,
Direct upgrade to cluster is not possible without installing SQL server in cluster aware mode. I would recommend you need to uninstall SQL server 2008 R2 and then create windows cluster between two nodes and then install SQL server in cluster aware
mode.
You are right with taking up complete backup of all databases with logins and jobs.
Please refer below link there is an alternate solution
How to move SQL server from standalone to cluster
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
My TechNet Wiki Articles

Full-text search not available after upgrade from SQL 2008 R2 Std to SQL 2012 Std

We upgraded our production SQL Server from 2008 R2 Std to 2012 Std last week, and the installation logs show everything was successful, but now we are unable to do any searches against our full-text indexes. The resulting error is as follows:
"Full-Text Search is not installed, or a full-text component cannot be loaded."
When executing the query "SELECT FULLTEXTSERVICEPROPERTY('ISFULLTEXTINSTALLED')", the result is "0". The "Full-Text Daemon Launcher service is also running. When running installation again to add the feature, it shows
"Full-Text and Semantic Extractions for Search" as being installed and unavailable for selection in the list of features to add. As a side note, we did the same upgrade in our identical QA environment before production and everything was successful
and full-text searches are working correctly. We have run the "Repair" routine in the SQL Installation Center and it did not correct the problem.
The full-text catalogs still appear when browsing through the GUI in SSMS or querying sys.fulltext_indexes and sys.fulltext_index_columns. It is not possible to view the properties of the catalog in SSMS, though, as the GUI throws an error and an empty
dialog box is shown. Any other thoughts?
Thanks,
AJ

I have no idea what is going, but assuming that it is a little pressing to get this fix, I think the best path in this case is to open a case with Microsoft.
Erland Sommarskog, SQL Server MVP, [email protected]

Migrate from SQL2000 (SQL_Latin1_General_CP1_CI_AS) To SQL 2008 (Arabic_CI_AS ) for Arabic

Dear Support,
We have SQL Server 2000 with collation SQL_Latin1_General_CP1_CI_AS. We have the data indexed in Arabic.
We have an archiving solution (File360 from OpenText) which is connected to SQL server database and we were able to
read arabic through the system.
Now we need to upgrade SQL server from SQL2000 to SQL2008 for the latest version of archiving solution (which supports
SQL2008 -> SQL2012)
We created new database in SQL2008 with collation Arabic_CI_AS. Then We migrated the data using Backup-Restore method
into this database. We found the database collation converted to Arabic_CI_AS from SQL_Latin1_General_CP1_CI_AS, but
the column collation remain same (ie SQL_Latin1_General_CP1_CI_AS).
With SQL_Latin1_General_CP1_CI_AS collation, the output for "select ID_1032 from EP13_10 where ID_14=422394" was in
???? format.
We altered the column collation manually using the sql
"alter table ep13_10 alter column ID_1032 char(250) COLLATE ARABIC_CI_AS"
Then also the result was in same ???? format. But we could able to read and write arabic for new records.
We need a solution to convert our old data to Arabic_CI_AS collation.
Is there any alternate way of migrating the data ?
Kindly guide us how to proceed.
Thanks & Regards

We created new database in SQL2008 with collation Arabic_CI_AS. Then We migrated the data using
Backup-Restore method
into this database. We found the database collation converted to Arabic_CI_AS from SQL_Latin1_General_CP1_CI_AS, but
the column collation remain same (ie SQL_Latin1_General_CP1_CI_AS).
Hello,
The effective collation is define on column level, the Server/database collations are only default values.
The backup is a real 1:1 copy of the database and when you restore the old database to a newer server, you can a again a real 1:1 copy and that's why the column collation remains the same.
One Option is to create a new database with the required collation. Restore the old database under a different name; then you can copy the data from the old database into the new one.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL 2008 settings for remote connections

Hi
I am unable to connect to my SAP B1 instance from a client PC. I am using SQL Server 2008 for the first time. The error message on the client PC implies that remote access has not been enabled on the SQL Server 2008. I am not sure how to do this and have so far found nothing from SAP.
Hope someone can help since I need this working for tomorrow!
Ian

SQL 2008 needs new SQL Native Client. Have you install that client on the PC successfully?
Thanks,
Gordon

SQL 2008 SP1 to SQL 2008 R2 Upgrade

I have a SQL server running SQL 2008 SP1 and am trying to upgrade to SQL 2008 R2. The server has an installation of SCOM 2007 R2 with CU4 on it with reporting services and SCOM data warehouse
The SQL upgrade advisor runs and tells me that Custom report items were detected on the report server and 3x Custom extensions or assemblies were detected on the report server
If I actually try to run the upgrade I get a 2 failures in the Upgrade Rules check:
No Custom Security Extensions and No Custom Authentication Extensions
I can see that the file rsreportserver.config has the custom entries relating to the scom data warehouse user so it is possible to change this file back to the original config file that was present before installing scom data warehouse and then run the sql
upgrade and then put the config file back?

Hi Mickpell,
Me too facing the same issue while upgrading from SQL 2008 SP1 to SQL 2008 R2. Getting below error:
No Custom Security Extensions and No Custom Authentication Extensions
Did u follow the steps you mentioned and it is Success???. Could you please confirm. If it was success, I can proceed with the same steps. Thanks in advance!!! I am
using SCOM 2007 R2 CU5. Should I download latest Hotfix Utility or CU2 utility is enough???
Regards, Suresh

SQL 2008 R2 In-Place Upgrade or Fresh Install to SQL2104

We have a server running Windows 2008 R2 and SQL 2008 R2 currently. We will call it SQL01. This houses databases for about 8 different applications and also has the name hard coded into a lot, I repeat, a lot of various things.
We are at the point where one of our applications needs to be upgraded and it only works with SQL 2014. So we need to either do an in-place upgrade or fresh install.
The obvious choice to me as a system admin is to do a fresh install, but the development side of the department knows how many places the name "SQL01" is hard coded and they want to do an in-place upgrade to avoid all the issues that would show
up if we changed names.
I have several questions, and I'd appreciate that the answers address them all if possible.
1. What are people's experiences with in-place upgrades from SQL 2008 R2 to SQL 2014?
2. To avoid this naming and coding issue, do companies use a permanent alias for their SQL servers? Like with exchange, we have an alias or A record pointing "mail" to the current Exchange server. As we do upgrades and the Exchange
server names change, the "mail" entry will always be pointed to the current one. Do people do this for SQL as well to avoid our issue of hard coding names?
3. I've head that you can also have both SQL 2008 R2 and SQL 2014 on the same server running together. This really doesn't help though if the SQL 2014 instance would need to be something other than the default which everything is currently pointed
to correct?
4. Is there any advice about a better way to go about this? Or a better way to do this moving forward? Other than not hard coding which I can't change now?
Thanks!

Hello,
Adding to the answers provided above, please consider discontinued features no longer available on SQL Server 2014.
I often see company configuring SQL Server aliases when installing SQL Server on SharePoint environments. You can certainly use DNS or use the following article.
http://msdn.microsoft.com/en-us/library/ms190445.aspx
An in-place upgrade is easier but is difficult to rollback in case something goes wrong. Meanwhile, a side-by-side upgrade provides you more control over what is upgraded, it keeps the legacy server online during the upgrade allowing you to easy rollback if
needed, but is not an automated process and the instance will not keep the same name, requiring you to use aliases or other ways to avoid client redirection.
Since you cannot change the application, go for a side-by-side upgrade and try the DNS alias or the client-side alias as I provided the procedure above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Essbase 7.1.3 rules support SQL 2008

Hello All,
We have some rule files which retrrive data from SQL 2005 and we have upgraded to SQL 2008 now since then we are unable to connect to the sql server using the essbase rules.
Did any one know whether MS SQL 2008 support essbase 7.1.3 rules?
Thank You

I think it would be dependent on the ODBC drivers you are using not Essbase itself.

After Upgraded to SQL 2012 Iam getting several Errors in SCCM 2007

After I upgrade my sql 2008 to sql 2012, I am getting several errors in SCCM 2007.Please find the below screen short
Configmgr reporting service point - Critical
SMS-Collection-Evaluator -critical
SmS-dstribution Manager -Critical
SMS-SRS reporting point -critical
SMS-Discovery Data manager -critical
SMS-Status Manager -critical
SMS policy Manager -critical
How can I resolve this issue.

I updated the path still I have the same problem...several error message found in SCCM server.please find the below one error message
On 7/21/2013 10:51:16 AM, component SMS_DISCOVERY_DATA_MANAGER on computer DCD-SCCM reported: SMS Discovery Data Manager failed to process the discovery data record (DDR) "", because it cannot update the data source.
Possible cause: On a Primary site, it is probably a SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that SMS can access the SMS site database.
5. Verify that the SMS site database, transaction log, and tempdb are not full.
6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console.
If the problem persists, check the SQL Server error logs.
Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server.
Solution: Make more space available on the site server.
how can I resolve the issue??

BPC 7.5 SP4 Support for Windows 2008 R2 and SQL 2008 R2

The release notes for BPC 7.5M SP04 state that support has been added for both Windows 2008 R2 and SQL 2008 R2.
For SQL 2008 R2, there is nothing in the feature pack described as "SQL 2005 Backward Compatibility Components" - which was a required piece for BPC 7/7.5 on SQL 2008. Is the SQL 2008 version still a requirement, or does BPC 7.5 now not need the Backward Compatibility components?
Also, the ReprotViewer executable that is packaged with BPC 7.5 is the one for SQL 2008- will that work when installing SQL 2008 R2?
thanks,
Tony DeStefanis
Column5 Consulting

Hi,
we have the same environment (BPC 7.5 SP4 on Windows 2008 R2 64 bit and SQL Server 2008 R2 64bit).
we are developping our application-set and for the moment we have no problem.
regards
massimo

Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

Our SharePoint 2013 Farm runs on ISCSI Disk on Windows 20008 R2 Standard SP1 Platform with SQL 2008 R2 Standard SP2.
Now we are planning to move this ISCSI Disk to another SQL 2012 Standard Platform and then upgrade the SQL 2008 Databse to SQL 2012. Can some one please let me know what challenges we might face during this implementation.

http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx
It depends if you want to move all, or just some, of your databases to the new server. If you need to move all of them that link describes the process but in short;
Backup and restore all databases to the new server
Configure the server roles and logins for the SharePoint accounts on SQL
Create (or modify) your SQL alias to point to the new server

SQL Server 2005 High Availability and Disaster Recovery options

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
Ione

DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA

SQL 2008 On SBS 2011 Question

Hi.
We have an sbs2011 std server.
We are looking at a new accounts package that requires SQL 2008 r2 (not express).
Our first thought was to purchase the premium add on but we can not find a single stockist in the UK that has one left for sale.
So is the only option to purchase another server with server OS and SQL 2008r2 STD on it if so this would be very very expensive.
We have also been made aware of SQL 2008 r2 for SBS, if this is OK to run the new accounts with then can this version of SQL be installed on SBS 2011 as we have found an copy that is for 1 server 5 cals for £600 (not sure how we buy more cals though as we
would need 6 users)
I would appreciate any advice on this situation.
Many thanks for you time

Hi:
It has been awhile since I have thought about this, but looking up the requirements for SQL 2008 for SBS I find this:
http://blogs.technet.com/b/sbs/archive/2009/03/23/requirements-for-installing-sql-2008-standard-edition-for-small-business.aspx
It appears it would work, and iirc the PAO was added for SBS 2011 because of the need to add a second server for SQL because Exchange 2010 uses so many resources on SBS 2011.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

How to overwrite existing DB's in SQL 2008?

I use Maintenance Plan of SQL 2008 Server for Backup some DB's. As a result i need to keep, only one set of Backup Up's and not more. So actually i can use Maintenance Plan Clean Up wizard, but i need something like Overwrite. That mean
i don't want do delete DB's after i finish Backup UP, but i want to overwrite existing backups?
Thanks.

Maintenance Plans are great as a base starting point for, "maintenance". They provide quick, easy setup and just get something in when in some cases, a fulltime DBA is not around.
Uri's recommendation on avoiding Maintenance Plans probably should have come with an explanation with such a strong statement. I'm guessing with the following, there will be an agreement...
Maintenance Plans, like I said, offer quick development of maintenance tasks. However, you can find yourself being restricted if you only use them for all of your maintenance tasks. This proves to make it difficult when you start getting further
into truly managing your database servers as they grow. Now, WITH INIT is an option form memory in the BACKUP Task but given the task, the conversion to calling the BACKUP DATABASE [db] TO DISK=N'filepath' WITH INT is a pretty quick change (at this point).
It will allow you to better understand the tasks you are refining as well. But, you do have the ability to leave it there.
I'm also not fully agreeing that WITH INIT is your best option if you want to retain backup history. If you do not, then by all means, INIT it all day. You may want to consider bringing this into SSIS or even a more structure TSQL statement to
dynamically create backup files by timestamps so you can at least retain some historic recovery abilities. Possible this is something of a secondary backup so that is based on my assumptions
Ted Krueger
Blog on lessthandot.com @onpnt on twitter

Upgrade MS SQL 2005 to MS SQL 2008 (R2) for High-Availability SAP ERP System

Similar Messages

Maybe you are looking for