Tuesday, May 14, 2013

[SQL 2012] Change database collation

[SQL 2012] Change database collation


Change database collation

Posted: 13 May 2013 06:02 PM PDT

Hi all, I have a db that i am restoring from a SQL 2005 server to 2012, which is in the wrong collation (It was wrong for the old server as well). From what I understand if you do a ALTER DATABASE this will only change future data and the current data will still be in the old collation? I found the following KB:[url=http://support.microsoft.com/default.aspx?scid=kb;en-us;325335]http://support.microsoft.com/default.aspx?scid=kb;en-us;325335[/url]Is this still the only way to update everything to a new collation (the kb says its for 2000 and 2005)? or in 2012 can you get away with just an ALTER DB?Hope someone can help.

PWAIT_MD_RELATION_CACHE and MD_LAZYCACHE_RWLOCK wait types

Posted: 22 Apr 2013 04:03 AM PDT

I'm hoping someone can give me some more information on either of these two wait types PWAIT_MD_RELATION_CACHE and MD_LAZYCACHE_RWLOCK. We started seeing these happen on queries that were accessing a table with 1,000 records, most of the waits were over a couple minutes. No blocking was occurring at the time, and other queries against the database were able to complete successfully. From doing a bit of research I was able to find this description on MSDN for PWAIT_MD_RELATION_CACHE: "Occurs during internal synchronization in metadata on table or index." This made me believe the issues was revolving around a large insert, update or delete that was occurring during that time, or manipulation of an index on the table. No records had been inserted or updated in the last 3 days, the indices were last rebuild 2 days prior to the issue. I've been unable to find anything in relation to MD_LAZYCACHE_RWLOCK.We are currently running Microsoft SQL Server 11.0.2100.60.Any help or ideas would be appreciated.

Same SQL Server Instance name on two different Windows 2008 R2 servers

Posted: 13 May 2013 08:09 AM PDT

Hi, We have two different Windows 2008 R2 servers (Server1 and Server2) on the same domain. The questions I have are:1) Can I have the same named instance on both the servers (Server1\Instance1, Server2\Instance2)?2) Will this cause any problems for operations.Thanks in advance for the replies.Raghuveer S

Backup Setup with AlwaysOn

Posted: 13 May 2013 07:12 AM PDT

I'm setting up my first pair of Sql 2012 servers using AlwaysOn. I set up backups to run on the primary and I understand that you can set up backups to run on both the primary and secondary servers but the secondary will fail. Is there a way I can stop the secondary server from sending out error messages about failed backups? Is it possible to script it so that the server looks at whether it's primary or secondary and turns on or off alerts based on that?Thanks for any help in advance.-tim

Storage for SQL 2012 and Exchange 2013

Posted: 13 May 2013 08:31 AM PDT

HelloI am planning for a storage using Dell MD3200f with 7x600GB 15K SAS HDD, 4x4TB NL-SAS HDD. This will cater SQL 2012 Std and Exchange 2013 Std for 100 users.This is NOT a virtualized environment. I would create RAID 1 for OS on 300GB 15K HDD available on the server. However, rest of the data resides on the SAN. The expected database transaction is 3000 per minute & IOPS at 500. Plan A - Create RAID 10 across 6x600GB 15K, which will contain SQL application, SQL DB, TempDB, Log + Exchange Application. Mailbox will sit on RAID 5 using 4TB HDD. [Pro: HDD space well utilized]Plan B - Create RAID 10 across 4x600GB 15K, which will contain SQL Application, SQL DB, TempDB + Exchange Application. 2x600GB 15K RAID 1 will be used for log. Mailbox will sit on RAID 5 using 4TB HDD. [Pro: Log is on separate HDD, Con: RAID 1 used for log is under utilized]Plan C - Create RAID 1 using 600GB 15K for SQL DB, Create RAID 1 using 600GB 15K for TempDB, log. RAID 1 using 600GB 15K for SQL Application, Exchange Application. Mailbox will sit on RAID 5 using 4TB HDD. [Con: HDD capacity cannot be well utilized]Which of the above would be recommended?Thank you in advanceGeorge

No comments:

Post a Comment

Search This Blog