No Extra Return from Stored Procedure

set nocount on; set ansi_warnings off;

Force Client to Download new resource files

Code behind //add the version number to the css and js link string host = Request.Url.Host; if (host.ToLower().IndexOf("dev") > 0 || host.ToLower().IndexOf("test") > 0) { Random rnd = new Random(); version = rnd.Next().ToString(); } else { version = ConfigurationSettings.AppSettings["app_version"]; } https://www.iis.net/configreference/system.webserver/staticcontent/clientcache

Best Time to Buy and Sell Stock II

Question

Say you have an array for which the ith element is the price of a given stock on day i. Design an algorithm to find the maximum profit. You may complete as many transactions as you like (ie, buy one and sell one share of the stock multiple times). However, you may not engage in multiple transactions at the same time (ie, you must sell the stock before you buy again).

Solution

1. Go through the price array;
2. If I don't have any stock in hands and today's price (i) is lower than tomorrow (i+1), I will buy in the stock
3. If do have stock and today's price (i) is higher than tomorrow (i+1), I will sale my stock and make profit.
4. Just sum up the profit.

Challenge

The main challenge of this question is to consider all the possible user cases.

1. The length of price can be less than 2. 
• If there is no price, we can not buy stock. 
• If there is only one price, we can buy stock but not sell it.
2. The price can be 0;
• My first solution thinks that the price of buying in stock is equal to zero when there is no stock in hands. However, it ignores the scenario that we can buy the stock in zero price.
3. To avoid the out-of-index exception, the for-loop will be end at the price before the last one (prices.length - 1). If I still have stock in hand after the for-loop and I have profit, I will sale my stock.

Code (Java)

public class Solution {
    public int maxProfit(int[] prices) {
        int m = 0; // save the profit
        int buyINPrice =-1; // save the price and indicates if I have stock in hand or not
        int i;
        if (prices.length >= 2) {
            for (i=0;i<prices.length-1;i++) {
              if (buyINPrice == -1 ) {
                  // when I have no stock
                  if (prices[i] < prices[i+1]) {
                      buyINPrice = prices[i];
                  }
              } else {
                  // when I have stock
                  if (prices[i] > prices [i+1]) {
                      m = m + (prices[i] - buyINPrice);
                      buyINPrice = -1;
                  }
              }
            }
            if (buyINPrice >= 0) {
                if (prices[i] > buyINPrice) {
                          m = m +  (prices[i] - buyINPrice);
                          buyINPrice = 0;
                }
            }
            return m;
        } else {
            return 0;
        }
    }
}

How to show line number in SQL Server Management Studio

Open MS SQL Server Management Studio

Click Tools -> Options

Expand Text Editor->All Languages->General on the left menu. Then select Line Numbers check box available under Display section.

AVD path problem

We can test our Android program on the Android Virtual Device (AVD).  An AVD is a device configuration for the Android emulator that allows you to model different device configurations.

By default, the AVD is saved in \\data\<<username>>\.android\avd. For some reasons, Eclispe doesn't go to the correct path to look up the configuration. User will receive error like "Failed to parse properties from config.ini".

One solution is to define the path by setting up a system variable. See the following instruction:

1. Start Menu > Control Panel > System > Advanced System Settings (on the left) > Environment Variables


2. Add a new user variable (at the top) that points your home user directory:

   Variable name: ANDROID_SDK_HOME
   Variable value: C:\Users\>User Name<

How Does Shrinking the Log File Work?

Shrinking the transaction log reduces its physical size by removing one or more inactive virtual log files. The unit of the size reduction is always the virtual log file. For example, if you have a 600 megabyte (MB) log file that has been divided into six 100 MB virtual logs, the size of the log file can only be reduced in 100 MB increments. The file size can be reduced to sizes such as 500 MB or 400 MB, but the file cannot be reduced to sizes such as 433 MB or 525 MB. A virtual log file that holds any active log records, that is, an active virtual log file, is part of the logical log, and it cannot be removed. For more information.


For a log file, the current size is the same as the total size of the pages that are used by the virtual log files. Note, however, that pages are not used by the log files. Virtual log files that hold any part of the logical log cannot be freed. If all the virtual log files in a log file hold parts of the logical log, the file cannot be shrunk. Shrinking is not possible until after log truncation marks one or more of the virtual log files as inactive.


A shrink-file operation can remove only inactive virtual log files. If no target size is specified, a shrink-file operation removes only the inactive virtual log files beyond the last active virtual log file in the file. If a target size is specified, a given shrink-file operation removes only enough inactive virtual log files to approach but not exceed the target size. After shrinking, the log file is typically somewhat larger than the target size, and it will never be smaller. The virtual log files make it difficult to predict how much the log file will actually shrink.


When any file is shrunk, the space freed must come from the end of the file. When a transaction log file is shrunk, enough virtual log files from the end of the log file are freed to reduce the log to the size requested by the user. The target_size specified by the user is rounded to the next highest virtual log file boundary. For example, if a user specifies atarget_size of 325 MB for our sample 600 MB file that contains six 100 MB virtual log files, the last two virtual log files are removed and the new file size is 400 MB.


If part of the logical log in the virtual logs does extend beyond the target_size mark, the SQL Server Database Engine frees as much space as possible and issues an informational message. The message tells you what actions you have to perform to remove the logical log from the virtual logs at the end of the file. After you perform this action, you can then reissue the DBCC statement to free the remaining space.

For example, assume that a 600 MB log file that contains six virtual log files has a logical log that starts in virtual log 3 and ends in virtual log 4 when you run a DBCC SHRINKFILE statement with a target_size of 275 MB, which is three-quarters of the way into virtual log 3:

Virtual log files 5 and 6 are freed immediately, because they do not contain part of the logical log. However, to meet the specified target_size, virtual log file 4 should also be freed, but it cannot because it holds the end portion of the logical log. After freeing virtual log files 5 and 6, the Database Engine fills the remaining part of virtual log file 4 with dummy records. This forces the end of the log file to the end of virtual log file 1. In most systems, all transactions starting in virtual log file 4 will be committed within seconds. This means that the entire active portion of the log is moved to virtual log file 1. The log file now looks similar to this:

The DBCC SHRINKFILE statement also issues an informational message that states that it could not free all the space requested, and that you can run a BACKUP LOG statement to free the remaining space. After the active portion of the log moves to virtual log file 1, a BACKUP LOG statement truncates the entire logical log that is in virtual log file 4:

List AD Group Member

The easy way to get the member list of a group in Active Directory is using the following command in Active Directory Module for Windows PowerShell.

Get-ADGroupMember G1 | FT Name

Notes
Get-ADGroupMember: command name
G1: group name
FT Name: full name of user