Thursday, May 23, 2013

[SQL 2012] SQL Server High availability step by step guide

[SQL 2012] SQL Server High availability step by step guide


SQL Server High availability step by step guide

Posted: 23 May 2013 12:14 AM PDT

Can anyone recommend a good step by step guide/article to setting up high availabilty

SQL 2012 with SharePoint 2010 question!

Posted: 08 Jan 2013 11:12 PM PST

We are having a tough time with this, and I don't know who to ask since it overlaps with SQL and SharePoint, so I am hoping someone here has some insight for us![b]Quick version:[/b]SharePoint 2010 has a special app called [url=http://technet.microsoft.com/en-us/library/ff686793(v=office.14).aspx]PrerequisiteInstaller.exe[/url] that installs SP2010 prerequisites, including three SQL Feature Pack components: SSRS Add-in, ADO and SQL Native Client. But those prerequistes seem to be SQL Server [b]2008[/b]-specific. We are using SQL [b]2012[/b], so we want to get PrerequisiteInstaller.exe to work with the SQL 2012 components. Does anyone know how to do this?[b]Long version:[/b]We have already built a nice SharePoint 2010 slipstreamed .iso with the latest Service Pack, Cumulative Update, and the SQL 2008 R2 prerequisites.But now we would like to build a new .iso with the SQL 2012 with SP1 prerequisites for SharePoint 2010. We tried this, but it fails.It seems the problem is with the SharePoint 2010 PrerequisiteInstaller.exe not recognizing the new SQL 2012 SP1 files.The three specific files are the SQL Native Client, ADO, and SSRS Add-in. We tried to just use the same command line switches, but point to the new files. Our command lines look something like this:/SQLNCli:file - Install Microsoft SQL Server 2008 Native Client from file/SQLNCli:"C:\SP2010 Prerequisites\Microsoft SQL Server 2008 R2 SP1 Native Client\sqlncli.msi"/ADOMD:file - Install Microsoft SQL Server 2008 Analysis Services ADOMD.NET from file/ADOMD:"C:\SP2010 Prerequisites\Microsoft SQL Server 2008 R2 ADOMD.NET\SQLSERVER2008_ASADOMD10.msi"/ReportingServices:file - Install SQL 2008 R2 Reporting Services SharePoint 2010 Add-in from file/ReportingServices:"C:\SP2010 Prerequisites\Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint 2010\rsSharePoint.msi"Just replacing the files with the corresponding SQL 2012 SP1 files does not seem to do the trick.Might any of you encountered this? If so, might you know how to get this to work? We really just want to get the SharePoint 2010 PrerequisiteInstaller.exe to recognize the new SQL 2012 SP1 files.Any help or insight appreciated!

SQL server media not supported on a X86 system error soon as setup is launch

Posted: 25 Feb 2013 09:15 PM PST

Hi! I am new in this forum and so excited to meet people who live and breath SQL!Besides being new in this forum, I am new to SQL as well so forgive me if I will ask newbie and "stupid" questions :-)Now on to my problem.I am trying to install an SQL server 2012 developer edition with SP1 X64 to my local machine and received this error "SQL server media not supported on a X86 system. To continue, run the SQL server setup media that matches your system"What have I done wrong?A few more information prior to the installation :- Operating System is Windows 8 on a dual boot MacBook pro- I allocated 81GB space for Windows system. No application installed yet. SQL would be the first- I uncompressed the .iso file to a USB drive and to my hard drive then run setup.exe from both but still had the same problemI suspect that it is because I am trying to install through a different media other than a DVD disc but I do not have available disc right now so I took my chance. I wasn't successful. What is the work around with this problem?Has anyone encountered this problem before? I need all the help please because I am aiming to take certification exams and this is my initial step so I can practice and review on my spare time.All help will be appreciated.thanks!

Can't find options to retain partitions in SSAS Tabular Deployment?

Posted: 04 Mar 2013 11:05 AM PST

So I have created a new Tabular cube on 2012, deployed it for a while. And created a few new partitions via SSMS in the server to cover all the data. Now I have made some changes in the project, planning to deploy it to the server, but can NOT find an option to ignore existing partitions (that are not defined in the project itself) I have tried it on a test db, and no matter what i do... the project seems to deploy its definition, and overwrite what's on the server. meaning all the partitions that i created after deploy are WIPED! I have billions of rows of data, so reprocessing all the missing partitions are really not preferable... and managing the partitions in project but not in ssms is also not preferable as we typicall use scripts to add / manage partitions after it goes livewe have found some blog posts about changing .deploymentoptions file... but we don't know what value we should change to (not in BOL).. we changed it to "RetainPartitions" as a test.. but that doesn't workanyone has been through this? thanks

Restoring a DB into an availability group - efficiency

Posted: 22 May 2013 03:29 AM PDT

Afternoon allI'm trying to restore three databases which are all in the primary node of a SQL2012 AlwaysOn Availability Group. I know I can do this by restoring to the primary, backing up full and log from the newly restored primary and restoring those onto each secondary, but is there a more efficient way? I wondered whether I could restore my full source backup onto the primary, take a log backup of the primary, and then restore the full source backup and the log backup from the primary onto the secondary. The DBs are large so rather than burn hours trying it, I thought I'd ask here first whether that's possible, or whether there's another way. There is one confusing answer [url=http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/359a635f-442c-49e6-8ba0-84b638a44e74]here[/url] that suggests it can be done via tail log and log backups, so I had a crack at that but it didn't work as there was a break in the LSN chain large enough to drive a truck through.ThanksKev

No comments:

Post a Comment

Search This Blog