Saturday, September 21, 2013

[SQL 2012] screenshot on view

[SQL 2012] screenshot on view


screenshot on view

Posted: 20 Sep 2013 02:08 PM PDT

I had a table like this:[code="other"]Name StartTime EndTime--------------------------------abc 10:00 14:00bcd 10:05 12:32cde 13:10 14:08dfe 11:00 11:08[/code]We planning to create the view using sql commend to view the total clients in every 30 mins.[code="other"]Time Clients--------------------------------10:00 110:30 211:00 311:30 212:00 212:30 213:00 113:30 214:00 214:30 0[/code]May I know how to create this view....Thanks for your help....

Add additional SQL 2012 instance to Windows Failover Cluster

Posted: 20 Sep 2013 07:07 AM PDT

Hi All,I have a Windows Failover Cluster setup across 3 nodes with only 1 service/application running on it - which is SQL Server 2012. Everything works great, however now I need to add another SQL instance for an entirely different project. I have added an additional iSCSI volume to the failover cluster and it shows up just fine. At this point, how to I add an additional instance of SQL 2012 to this cluster using the new storage disk?I assume I'd just pop the SQL Server 2012 disc in one of the nodes and install a new SQL Server Cluster instance and then go around to the rest of the nodes and just use the 'add node' option, but I just wanted to verify first. I attempted to do this and got cold feet when it came to the part about installing the setup and support files. The reason I got cold feet was because we have a group of people using the existing SQL 2012 instance and I didn't want to disrupt anything.Can anybody please provide any instructions or steps for adding a new instance to my failover cluster?Thank you all!

Setting up multiple AG's on 1 server

Posted: 20 Sep 2013 04:31 AM PDT

Hi all, question for you please:i am upgrading sql from 2008 to 2012 and on one instance we have 3 databases setup with mirroring.The plan is to use AAG but i am not sure if i need to create one availabilty group with 3 databases or i can create 3 separate availabilty groups with 1 database in each availability group.What will be disadvantages/advantages with creating 3 separate availabilty groups with 1 database in each availability group? how about performance and server resources? it is used more resources when you have more AG's on the instance opposed to just 1?This AG will be setup as synchronous with auto failover.The reason why i am thinking to setup 3 separate availabilty groups with 1 database in each availability group is because if for some reason the database is not in synchronous mode i can easily remove replica until the problem is solved for just 1 database instead of 3.

No comments:

Post a Comment

Search This Blog