Thursday, September 5, 2013

[SQL 2012] Upgrading from SQL 2008 R2 to SQL 2012 R2

[SQL 2012] Upgrading from SQL 2008 R2 to SQL 2012 R2


Upgrading from SQL 2008 R2 to SQL 2012 R2

Posted: 05 Sep 2013 01:40 AM PDT

We're finally going to be upgrading our old SQL Server 2005 instance, to SQL Server 2012 R2. Therefore I need to upgrade my development environment as well. Currently, on my dev box I'm at SQL Server 2008 R2 Developer Edition, I want to upgrade to SQL Server 2012 R2 Developer Edition. Do I uninstall 2008 R2 and then install 2012 R2? Or do I do something different?

SSRS 3.0 Parameters input issue

Posted: 18 Aug 2013 09:32 PM PDT

Hi all,I am building a report that will make a comparison with figures for the last 3 months, and last 12 months. For this I will build 3 datasets with the exact same structure, with the difference that I need each one of them the data will be different.The way I am trying to do it is to go to a specific dataset and on the parameters tab choose the parameter and do as example below:=Parameters!Period.Value-3 The parameter above would be for the dataset that needs to show the figures for the last quarter, the period field is an integer and every month as a number attached, so I figured that if for this specific dataset in the parameters tab there is an instruction for the parameter in the expression it should work... It doesn't, anyone has a suggestion for this?Best regards,Daniel

Is there a way of copying the securables definitions from 1 db to another?

Posted: 05 Sep 2013 01:49 AM PDT

We're finally moving to SQL 2012 from SQL 2005. Is there a way of automating the moving or copying of securables from the old database for some of the users, to the new database for the same users? If so, how is that done?

what is the best way to copy database from 2012 to 2008r2

Posted: 04 Sep 2013 05:31 AM PDT

Hi EveryoneI am asked to copy and move database from 2012 instance to 2008r2 instance; those are on separate VM(virtual machine)i know backup and restore does not work in this case.i am trying to do it by using Generate scripts option, i am not sure how long its going to be succeed.I tried Export and import tool, but i failed, may be due to my inefficiency of operating the toolMay i know what is the best way to do this job??:hehe:

Backups \ Maint Jobs AlwaysOn SQL 2012

Posted: 16 Aug 2013 03:00 AM PDT

Hello all, I have installed and completed a AlwaysOn 2 node VM failover cluster, what fun :-D! I was starting to setup the backup jobs and ran across how AlwaysOn works with this. A little back ground, we slammed this in to meet a deadline and boot contractors out so my learning was put on hold until after we went live, Ya me as the DBA!So I went and change the back preference to Any Replica, this allowed me to back up the primary node and place the tlog BU, re-index, checkdb, update stats, clean files jobs. Now the secondary replica I want to backup as well. The notes I had read from a MVP DBA had said that if I used Any Replica I could backup both...No Dice! I can put a copy only full backup on the secondary but it will not backup the user database, just master and MSDB.I also found the Exclude Replica option but cannot get a clear explanation on it, it could be the lack of sleep I have had over the past week slamming this into Prod, which I am not happy about but thus is the life of a DBA, right! I am sure we all know!Besides the backup, I want to setup Maint. Jobs on both. Now I know that AlwaysOn is Mirroring and FCI, it works, great, I know if I rebuild some indexes it will copy over to the secondary, that's great too however this is two separate databases so I want them both the be clean. :)So my questionsa. How can I backup both P and S?b. What Maint. Jobs should be set up on each?Thanks!

Sql Server 2012 installation Error

Posted: 04 Sep 2013 11:25 PM PDT

Hi everyone, I hope I can find some help on my Sql Server 2012 Evaluation(x86).While installing I am getting this error.This is my error log.Overall summary: Final result: Failed: see details below Exit code (Decimal): -2061893607 Start time: 2013-09-05 14:00:40 End time: 2013-09-05 14:21:22 Requested action: InstallSetup completed with required actions for features.Troubleshooting information for those features: Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.Machine Properties: Machine name: B Machine processor count: 4 OS version: Windows 7 OS service pack: Service Pack 1 OS region: United States OS language: English (United States) OS architecture: x86 Process architecture: 32 Bit OS clustered: NoProduct features discovered: Product Instance Instance ID Feature Language Edition Version Clustered Package properties: Description: Microsoft SQL Server 2012 Service Pack 1 ProductName: SQL Server 2012 Type: RTM Version: 11 Installation location: D:\SQLServer2012SP1-FullSlipstream-ENU-x86\x86\setup\ Installation edition: Evaluation Slipstream: True SP Level 1 Patch Level: 11.1.3128.0Product Update Status: Success: KB 2674319, KB 2793634Product Updates Selected for Installation: Title: Service Pack 1 Knowledge Based Article: KB 2674319 Version: 11.1.3000.0 Architecture: x86 Language: 1033 Title: SQL Server 2012 SP1 GDR Product Update Knowledge Based Article: KB 2793634 Version: 11.1.3128.0 Architecture: x86 Language: All Update Source: MUUser Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: false AGTSVCACCOUNT: NT Service\SQLSERVERAGENT AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Manual ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup ASCOLLATION: Latin1_General_CI_AS ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log ASPROVIDERMSOLAP: 1 ASSERVERMODE: MULTIDIMENSIONAL ASSVCACCOUNT: NT Service\MSSQLServerOLAPService ASSVCPASSWORD: <empty> ASSVCSTARTUPTYPE: Automatic ASSYSADMINACCOUNTS: B\RADIRAE ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp BROWSERSVCSTARTUPTYPE: Disabled CLTCTLRNAME: CLTRESULTDIR: C:\Program Files\Microsoft SQL Server\DReplayClient\ResultDir\ CLTSTARTUPTYPE: Manual CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client CLTSVCPASSWORD: <empty> CLTWORKINGDIR: C:\Program Files\Microsoft SQL Server\DReplayClient\WorkingDir\ COMMFABRICENCRYPTION: 0 COMMFABRICNETWORKLEVEL: 0 COMMFABRICPORT: 0 CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130905_135732\ConfigurationFile.ini CTLRSTARTUPTYPE: Manual CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller CTLRSVCPASSWORD: <empty> CTLRUSERS: B\RADIRAE ENABLERANU: false ENU: true ERRORREPORTING: false FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK FILESTREAMLEVEL: 0 FILESTREAMSHARENAME: <empty> FTSVCACCOUNT: NT Service\MSSQLFDLauncher FTSVCPASSWORD: <empty> HELP: false IACCEPTSQLSERVERLICENSETERMS: true INDICATEPROGRESS: false INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\ INSTALLSHAREDWOWDIR: <empty> INSTALLSQLDATADIR: <empty> INSTANCEDIR: C:\Program Files\Microsoft SQL Server\ INSTANCEID: MSSQLSERVER INSTANCENAME: MSSQLSERVER ISSVCACCOUNT: NT Service\MsDtsServer110 ISSVCPASSWORD: <empty> ISSVCSTARTUPTYPE: Automatic MATRIXCMBRICKCOMMPORT: 0 MATRIXCMSERVERNAME: <empty> MATRIXNAME: <empty> NPENABLED: 0 PID: ***** QUIET: false QUIETSIMPLE: false ROLE: <empty> RSINSTALLMODE: DefaultNativeMode RSSHPINSTALLMODE: DefaultSharePointMode RSSVCACCOUNT: NT Service\ReportServer RSSVCPASSWORD: <empty> RSSVCSTARTUPTYPE: Automatic SAPWD: ***** SECURITYMODE: SQL SQLBACKUPDIR: <empty> SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS SQLSVCACCOUNT: NT Service\MSSQLSERVER SQLSVCPASSWORD: <empty> SQLSVCSTARTUPTYPE: Automatic SQLSYSADMINACCOUNTS: B\RADIRAE SQLTEMPDBDIR: <empty> SQLTEMPDBLOGDIR: <empty> SQLUSERDBDIR: <empty> SQLUSERDBLOGDIR: <empty> SQMREPORTING: false TCPENABLED: 1 UIMODE: Normal UpdateEnabled: true UpdateSource: MU X86: false Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130905_135732\ConfigurationFile.iniDetailed results: Feature: Management Tools - Complete Status: Passed Feature: Client Tools Connectivity Status: Passed Feature: Client Tools SDK Status: Passed Feature: Client Tools Backwards Compatibility Status: Passed Feature: Management Tools - Basic Status: Passed Feature: SQL Server Data Tools Status: Passed Feature: Reporting Services - Native Status: Failed: see logs for details Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A0019 Error description: Could not find the Database Engine startup handle. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025 Feature: Database Engine Services Status: Failed: see logs for details Reason for failure: An error occurred during the setup process of the feature. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A0019 Error description: Could not find the Database Engine startup handle. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025 Feature: Data Quality Services Status: Failed: see logs for details Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A0019 Error description: Could not find the Database Engine startup handle. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025 Feature: Full-Text and Semantic Extractions for Search Status: Failed: see logs for details Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A0019 Error description: Could not find the Database Engine startup handle. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025 Feature: SQL Server Replication Status: Failed: see logs for details Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A0019 Error description: Could not find the Database Engine startup handle. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025 Feature: Distributed Replay Client Status: Passed Feature: Distributed Replay Controller Status: Passed Feature: Integration Services Status: Passed Feature: Data Quality Client Status: Passed Feature: Analysis Services Status: Passed Feature: SQL Browser Status: Passed Feature: Documentation Components Status: Passed Feature: SQL Writer Status: Passed Feature: SQL Client Connectivity Status: Passed Feature: SQL Client Connectivity SDK Status: PassedRules with failures:Global rules:Scenario specific rules:Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130905_135732\SystemConfigurationCheck_Report.htm

Impact of trace flag 272 on SQL Server 2012 apart from disabling identity jump

Posted: 04 Sep 2013 06:51 PM PDT

I am upgrading my application's SQL Server from 2008 R2 to 2012.As discussed in the below URL I am able to see the Identity jump after I upgrade and the server is restarted.Now since I cannot afford this and at this moment I do not have the time to create a sequence with NOCACHE and test it again I have to go ahead and add trace flag 272 in the start up parameter as this is the only solution which I can implement and even rollback without much hassles.[url=http://connect.microsoft.com/SQLServer/feedback/details/739013/alwayson-failover-results-in-reseed-of-identity][/url]I have searched a lot but nowhere I found any kind of documentation around this flag. What I got to know by reading several web literatures is, this flag will disable the new feature of IDENTITY property that has been implemented as part of SQL Server 2012 and will make it work like it was doing in SQL Server 2008 R2. [b]But I want to know implementing this flag would impact any other feature or performance (except the performance of IDENTITY, that I can bear with) of SQL Server.[/b]ThanksSoumyadeb

SSISDB deployed package run as windows user

Posted: 04 Sep 2013 11:44 PM PDT

HiI am trying to run a SSISDB deployed package by windows user but as per My requirements I cannot directly login as windows user to serverSo I tried using SQL agent job with run as user and putting the following code in stored procedure with execute as windows users[code="other"]EXEC [SSISDB].[catalog].[create_execution] @package_name=N'abc.dtsx', @execution_id=@execution_id OUTPUT, @folder_name=N'pqr', @project_name=N'abc', @use32bitruntime=False, @reference_id=NullDECLARE @var0 smallint = 1EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id, @object_type=50, @parameter_name=N'DUMP_ON_ERROR', @parameter_value=@var0EXEC [SSISDB].[catalog].[start_execution] @execution_id[/code]But it is not able to access a shared drive during execution which if the package directly run as windows user does work fineAny idea

SQL Server 2012 cluster install error

Posted: 11 Jun 2013 02:11 AM PDT

I am installing SQL Server 2012 Enterprise (x64) with SP1 on a Windows 2012 SP1 3 node cluster utilizing mount points. I get the following error during the initial install on the first node:While updating permission setting for Folder 'z:\SQLDATA\System Volume Information' the permission setting update failed for file 'z:\SQLDATA\System Volume Information\ResumeFilterKey.Store' The folder were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-617070787-1164103636-1191419902-1692725703-799689240)The 3 workarounds I found all referenced SQL Server 2008 R2. I tried all 3 suggestions and none have worked.I am thinking this relates to the mount somehow, but I am stuck. And, no, the mount points are NOT in the root of the drive.Any ideas???

No comments:

Post a Comment

Search This Blog