Wednesday, April 17, 2013

[MS SQL Server] Moving server to different zone in Datacenter

[MS SQL Server] Moving server to different zone in Datacenter

Moving server to different zone in Datacenter

Posted: 16 Apr 2013 11:38 AM PDT

I am involved in moving some servers to different zone within the same data-center. There are no IP changes, so I would think this is the same as normal server shutdown. The server will be out for more than 24 hours.In terms of DBA perspective, I was thinking about stopping the SQL services before they shutdown windows box, and start the SQL services after server up and running.Anyone have any other suggestions? Also, from app server side, do they need to be shutdown as well? If you had similar experience, or if you know the actual steps, please share.Thanks in advance,SueTons.

Data Warehouse Backup Strategy

Posted: 17 Apr 2013 02:21 AM PDT

We're migrating from SQL server 2000 to 2008 and I'm trying to come up with a backup strategy for our data warehouse on the new servers. I'm particularly focused on one DB that is most frequently used. I want to minimize the size of the backup file(s) and the impact that the backup has on the servers. Here is the background info:- We're a relatively small shop and so have limited resources (time). No dedicated full time DBA.- We currently load 100+ flat files each night to 100 + SQL tables. We're talking about 60-75 GB of data for these files/tables. We don't have access to only the changed records from the source systems, so the tables are dropped and re-created during each nightly load.-We also have numerous tables that persist – typically these are tables where the data files from the source system are so large they can't possibly be dropped/created each night. Instead, we extract a subset from the source system and insert/update the persistent tables. These tables account for about 150 GB.- The remaining tables in the DB take up another 100 GB. It's a mixed bag here in terms of availability requirements – some are important (in the event of failure, restore would need to be within 24 hours) others could wait a week or more.- In the current SQL 2000 environment, using a simple backup model, the backup is about 350GB uncompressed. This goes nightly to a SAN, and from there to tape offsite.For a multitude of reasons, we're not performing an all-at-once migration, so we'll have one SQL2K and two SQL2008 servers running simultaneously. If we took the overall same approach as we did in the past, that would amount to about 1.25 TB of backups…not desirable! Especially since much of the data is dropped/recreated.Aside from utilizing compression software (considering Redgate SQL Backup Pro), are there other ways to reduce backup overhead (processing resources and storage resources)? I thought perhaps we might do file backups with the persistent tables on primary, then the drop/load tables on secondary file(s), but it doesn't seem you can (safely/reliably) restore only some of the file groups. I've seen 'undocumented' ways of doing that, but I like to sleep at night…I thought about truncating the tables each night before the backup, but that will require significant redesign of existing processes in terms of timing etc. and resources are tight. I could do this with some of the largest tables that we drop/reload, but we also have some larger tables that we don't drop/recreate each night. That means this approach will help a bit.Any ideas that don't involve a complete redesign of the DB? If I had unlimited time and energy, I can see where separate DBs would be best (and not just for the backup strategy), but that's not practical for us.Also, This is my first post...so suggestions on etiquette/process are greatly appreciated.

CU installed or not?

Posted: 16 Apr 2013 05:55 AM PDT

We single node cluster running SQL 2008 R2 SP2. We noticed the Application Even Log contianing thousands of messages likeInformation DateTime SQLAgent$Name 53 Failover "[sqagtres] LooksAlive request."Information DateTime SQLAgent$Name 53 Failover "[sqagtres] CheckServiceAlive: returning TRUE (success)" I found [url=http://support.microsoft.com/kb/2718920]KB2718920[/url] which recomends installing Cunulative Update 3 for SQL 2008 R2 SP2. The Install reports that it failed. But when I restarted SQL serivce, it went into script update mode, and minutes later came online and reports that it is now version 10.50.4266.0. The end of the summary.txt file contains the following 2013-04-16 06:56:17 Slp: Attempting to run patch request for instance: MSSQLSERVER2013-04-16 07:11:30 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -595541211)2013-04-16 07:11:41 Slp: Error result: -5955412112013-04-16 07:11:41 Slp: Result facility code: 11522013-04-16 07:11:41 Slp: Result error code: 49957Much earlier in the file...2013-04-16 06:52:44 Slp: Package ID sql_fulltext_ctp6_Cpu64: Discovery: Package version data are " Installed Version: 10.52.4000.0 MinVersion: 10.0.1400 MaxVersion: 10.50.1599.1"2013-04-16 06:52:44 Slp: Package ID sql_fulltext_ctp6_Cpu64: Discovery: Package version data are " Installed Version: 10.52.4000.0 MinVersion: 10.0.1400 MaxVersion: 10.50.1599.1".....013-04-16 06:52:51 Slp: Patch Id KB2754552_sql_engine_core_shared_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_shared_Cpu64. Detail description of this patch package is: PatchId=KB2754552_sql_engine_core_shared_Cpu64 PatchVersion=10.52.4266.0 BaselinePackageId=sql_engine_core_shared_Cpu64 BaselineVersion=10.52.4000.0; PatchFileName=sql_engine_core_shared.msp PatchCode={A9F26DCE-10E2-4224-AC5F-2F78F1321DDD}2013-04-16 06:52:51 Slp: Patch Id: KB2754552_sql_as_Cpu64 - The baseline msi is not installed. The patch package is ignored.There seems to be a mismatch between the version of SQL installed and the version this installer was expecting, though I checked the links and the files I downloaded should be correct. Is anyone not confused by this? And is the instance I tried to install to trustworthy?

Why powershell?

Posted: 16 Apr 2013 09:01 PM PDT

Hi all experts,I have being reading about Powershell a lot this days. What i came to know about powershell is that , it is a powerfull tool to automate the daily process which a DBA usually Do.But when we do have Sp's running through Job , to do the same task, then why do we need PowerShell. Is this a redundant functionality given by SQL Server. Or am i missing the purpose of PowerShell?

Report Services / Upgrade from Standard to Enterprise

Posted: 16 Apr 2013 05:36 AM PDT

Hello - I am trying to do a an upgrade from Standard to Enterprise using the SQL Server Installation center (Maintenance | Edition upgrade)During setup I get the following error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."The summary file (shown in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130416_141115) shows it fails when it gets to report services.I followed the steps to remover report services http://msdn.microsoft.com/en-us/library/ms143518(v=sql.90).aspxStill, same error - I then tried installing Report Services to make it happy - but the setup thinks report services is still there. Any advice on either installing it or getting rid of Report Services so I can upgrade would be appreciated.Thanks in advance Dave
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog