Hardware has been ever increasing in strength, but SQL licensing has not reflected this except for charging more money due to the per core cost. We are in the information and data collecting age and Microsoft’s scale limitations (http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.110).aspx) for the versions of SQL might have been fine in the past, but they are not now.
Some examples of limitations that should change:
I had this error after I had installed SharePoint 2010 Foundation and tried to use search:
Your search cannot be completed because this site is not assigned to an indexer.
Browse to your Site Adminstration page and go to this page: http://servername:7777/_admin/cntdbadm.aspx change servername and port. Select your database name and in the Search Server section, you click the drop down and select server. Hit okay.
I’ve been selected as one of the top 10 finalists for the System Administrator of the Year from the editorial staff at Windows IT Pro and made it into the final round of voting, which is now live here:
Please vote before 8/31/2011
I got this error when trying to add a file to a full database:
Msg 0, Level 11, State 0, Line 0. A severe error occurred on the current command.
But, nothing was logged anywhere that gave me a hint as to what the problem was. I knew from past experience that sometimes if the first data file in a database is completely full, you will get an error like this. But, I had 33MB available. So, I gave it 50MB more and was able to add files to the database again. Hope this helps someone.
I installed SharePoint 2010 server on top of my existing foundation install that I was already using thinking that I could convince management to pay for it. Well, no go now, so I thought I would just uninstall Sharepoint 2010 Server and have my SharePoint Foundation sitting there ready to be used. NOT! It uninstalled everything! I didn't have a Sharepoint backup, just database backups. My databases were intact, but you can't just swap databases like you could in previous versions (I tried and failed).
This past weekend, I gave a talk at the Olympia, WA SQL Saturday conference on Transaction Replication. I am posting up my slide deck and script files for monitoring replication performance and last hours replication errors. Both of these procs need to be run on your distributor server and the prc_internalsendmail can be replaced with your mail proc of choice, including sp_send_dbmail.
In my organization, I happened to set up a transactional replication for the whole database (240 gb) on which I ran the snapshot and ended up time out multiple times and gave up that initializing a full database transactional replication is not going to work out for large databases.
Later I came across the following link to setup transactional replication and initializing with backup option.
This worked for me :-)
Windows 2008 failover cluster administrator is difficult to figure out. To failover to another node, you can use the UI or use the command line. The UI is easy as you can see in this image:
However, you can move the Cluster Group by using command line as follows
cluster group "cluster group" /move:sgjssdlvmrd057
Next, to get the cluster configuration of the quorum