Friday, May 3, 2013

[MS SQL Server] Upgrade production Server - SQL 2005 to SQL 2008 - inplace upgrade

[MS SQL Server] Upgrade production Server - SQL 2005 to SQL 2008 - inplace upgrade

Upgrade production Server - SQL 2005 to SQL 2008 - inplace upgrade

Posted: 02 May 2013 10:03 PM PDT

Hi All,Can I confirm that I have the process correct and that I have not missed anything ?I am currently running SQL Server 2005 and want to upgrade to 2008/R2 - I am running several databases, with triggers and Stored Procedures - also Maintenance Tasks.So ...Backup the DatabasesBackup / Document TriggersBackup / Document Stored ProceduresBackup / Document Maintanance TasksBackup / Document Agent JobsInstall Sql 2008 as an upgradeCheck DB integrityCheck T / SP / MT / AJ from abovecheck ERP system - functions in the same way and privilages have not been compromised during the upgrade.I think this should cover it ?

Index Fragmentation and SANs

Posted: 15 Mar 2012 07:55 AM PDT

OK, so this is a showdown. I have been looking all over the place and can only find vague references to SANs 'muddying' the issues of index fragmentation. I have always kept my index fragmentation on databases in check by rebuilding/reorganizing as necessary (code set referring to a dmv that tells me the % of fragmentation, and then it chooses which method, if either, to use). What I DON'T know is whether or not SANs change this. Is fragmentation seriously no longer a problem with SANs? I will admit, this sounds alien to me, but I don't know enough about SANs to be able to argue either way. Do I or don't I regularly defrag my indexes as a good practice in this realm?

The database principal owns objects in the database and cannot be dropped

Posted: 02 May 2013 05:57 PM PDT

Hi guys, Recently we got this error:The database principal owns objects in the database and cannot be dropped.The database version is SQL Server 2008,I have checked that user doesn't have schema,procedure,function,table,view and so on.My question is: how to check the user's objects?

Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222)

Posted: 02 May 2013 08:52 PM PDT

I stopped the backup job which was running for arround 2 days,now it is showing in rollback state since last 1 day,And rollback process is blocking the other processes,I am getting following error when trying to access the database through other server.Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222)

Local and remote database?

Posted: 02 May 2013 05:28 PM PDT

..

SQL Cluster Gateway Info Lost on Node Move or Failure Simulation

Posted: 19 Feb 2013 04:03 AM PST

Hello All,First time poster so if this has been asked, please forgive. I have searched the forums but didn't find what I was looking for.I have a 2 server node SQL Cluster, running on identical Dell hardware, in the same datacenter, in the same subnet, both running 2008R2 OS and SQL 2008R2. In addition, all network configurations on the NICs are statically entered on the servers and not being pulled via DHCP. We are using (2) NICs per server. One for the network and one for the cluster heartbeat.When the servers are rebooted and the SQL failover process runs its natural course, we do not lose any network configuration info on the networked NICs. All network info remains on both servers.If we log into either server and manually do a failover, either by "Move this service or application to another node" or "Simulate failure of this resource", the server that was the ACTIVE node loses its Gateway IP Info as soon as the failover completes. All other network info remains unchanged and intact.It doesn't matter which server we are on, and which server we are failing over to. The server with the ACTIVE node at the time of the failover loses its Gateway IP info but nothing else.This does not happen when failovers happen on their own due to server reboots (like patch days).All hardware and network configurations, with the exception of specific IP Address configs, are all the same.Any ideas?Thanks in advance for your time.Dan

Add features to an existing instance

Posted: 02 May 2013 06:39 AM PDT

Hi I need to install Full search and Analysis services to an existing instance of SQL Server 2012. When I run set up or click change from the control panel, setup does not see that the SQL instance is out there. What does it use to find existing instances to upgrade? Is it a registry entry or some sort of scan? I recently applied some hardening changes to the instance from a CIS benchmark so I don't know if that has anything to do with it.Any ideas how to get setup to see the instance?Howard
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog