Use:

    SET NOCOUNT ON

to suppress these messages and use the command below to enable the messages.

    SET NOCOUNT OFF

I am facing a continuing problem distinguishing delegation, composition and aggregation from each other, and identifying the cases where it&#39;s the best to use one over the other.

I have consulted a Java OO Analysis and Design book, but my confusion still remains. The main explanation is this:

**Delegation**: When my object uses another object&#39;s functionality as is without changing it.

**Composition**: My object consists of other objects which in turn cannot exist after my object is destroyed-garbage collected.

**Aggregation**: My object consists of other objects which can live even after my object is destroyed.

Is it possible to have a few simple examples demonstrating each case, and the reasoning behind them? How else can these examples be demonstrated other than my object simply having a reference to another object(s)?

Distinguishing between delegation, composition and aggregation (Java OO Design)

This is a follow up to my [initial question][1] and I would like to present my findings and ask for corrections, ideas and insights. My findings (or rather interpretations) come from people&#39;s answers to my previous question, reading MSDN .NET 3.5 documentation and debugging .NET 3.5 code. I hope this will be of value to someone who was wondering like me how to detect when an application terminates. 

**Events:**

 - `System.AppDomain.CurrentDomain.ProcessExit`: raised when process exits, e.g. after the default `AppDomain` and everything else was unloaded [Total execution time is limited to just 3 seconds!]. For WPF, use `System.Windows.Application.Exit` instead. For Windows Forms, run code after `Application.Run(...)` in main method.

 - `System.AppDomain.CurrentDomain.DomainUnload`: raised when an `AppDomain` other than default `AppDomain` unloads, e.g. when running classes with unit testing frameworks (MbUnit with TestDriven.NET).

 - `System.AppDomain.CurrentDomain.UnhandledException`: (if handled in default `AppDomain`:) raised for any unhandled exception in any thread, no matter what `AppDomain` the thread started in. This means, this can be used as the catch-all for all unhandled exceptions.

 - `System.Windows.Application.Exit`: raised when WPF application (i.e. the default `AppDomain`) exits gracefully. Override `System.Windows.Application.OnExit` to take advantage of it.

 - Finalizers (destructors in C#): run when garbage collector frees unmanaged resources. [Total execution time is limited!].


**Order of events:**

WPF application: graceful exit

1. `System.Windows.Application.Exit`
2. `System.AppDomain.CurrentDomain.ProcessExit`
3. Finalizers

WPF application: unhandled exception

1. `System.AppDomain.CurrentDomain.UnhandledException`

MbUnit running inside TestDriven.NET:  passed test (graceful exit)

1. `System.AppDomain.CurrentDomain.DomainUnload`
2. Finalizers

MbUnit running inside TestDriven.NET: failed test (unhandled exceptions are handled by MbUnit)

1. `AppDomain.CurrentDomain.DomainUnload`
2. Finalizers


**Questions:**

 - Are my interpretations/findings correct?
 - Do you know of more details that I have
   left out? E.g. what is the total
   execution time for finalizers?
 - Do you know of any other events /
   ideas that I be aware of?
 - What events are there and what order do they get raised in other applications, e.g. Windows Forms, Web Service, ASP.NET web site, etc?

  [1]: https://stackoverflow.com/questions/1368697/how-to-detect-when-main-thread-terminates

How to detect when application terminates?

Is there a command I can run inside my SQL script so that it stops outputing information about each operation that gets run?

ie I don&#39;t want to see this:

    (1 row(s) affected)
    
    (1 row(s) affected)
    
    (1 row(s) affected)
    

How to stop SQLServer writing extraneous stuff eg (1 rows affected)

Is there a command I can run inside my SQL script so that it stops outputing information about each operation that gets run?
ie I don't want to see this:
<pre><code class="hljs language-scss">(1 row(s) affected)

(1 row(s) affected)

(1 row(s) affected)
</code></pre>

My question is similar to [this](https://stackoverflow.com/questions/510012/get-a-list-of-dates-between-two-dates) MySQL question, but intended for SQL Server:

Is there a function or a query that will return a list of days between two dates? For example, lets say there is a function called ExplodeDates:

    SELECT ExplodeDates(&#39;2010-01-01&#39;, &#39;2010-01-13&#39;);

This would return a single column table with the values:

&lt;!-- language: lang-none --&gt;

    2010-01-01
    2010-01-02
    2010-01-03
    2010-01-04
    2010-01-05
    2010-01-06
    2010-01-07
    2010-01-08
    2010-01-09
    2010-01-10
    2010-01-11
    2010-01-12
    2010-01-13

I&#39;m thinking that a calendar/numbers table might be able to help me here.

----

**Update**

I decided to have a look at the three code answers provided, and the results of the execution - as a % of the total batch - are:

- [Rob Farley&#39;s answer](https://stackoverflow.com/a/1378788/1378788) : 18%
- [StingyJack&#39;s answer](https://stackoverflow.com/a/1378866/1378866) : 41%
- [KM&#39;s answer](https://stackoverflow.com/a/1378712/1378712) : 41%

*Lower is better*

I have accepted Rob Farley&#39;s answer, as it was the fastest, even though numbers table  solutions (used by both KM and StingyJack in their answers) are something of a favourite of mine. Rob Farley&#39;s was two-thirds faster.


**Update 2**

Alivia&#39;s [answer](https://stackoverflow.com/a/9207952/31532) is much more succinct. I have changed the accepted answer.

Get a list of dates between two dates using a function

I need to check if a specific login already exists on the SQL Server, and if it doesn&#39;t, then I need to add it.

I have found the following code to actually add the login to the database, but I want to wrap this in an IF statement (somehow) to check if the login exists first.

    CREATE LOGIN [myUsername] WITH PASSWORD=N&#39;myPassword&#39;, 
    DEFAULT_LANGUAGE=[us_english], 
    CHECK_EXPIRATION=OFF, 
    CHECK_POLICY=OFF 
    GO

I understand that I need to interrogate a system database, but not sure where to start!


Checking if a SQL Server login already exists

I created few user defined types in my database as below

    CREATE TYPE [dbo].[StringID] FROM [nvarchar](20) NOT NULL

and assigned them to various tables. The tables in my database are in various schemas (not only `dbo`)

But I realized I need bigger field, and I need to alter, e.g increase from `[nvarchar](20)` to `[nvarchar](50)`, but there is no `ALTER TYPE` statement.

I need a script that uses a temp table/cursor whatever and saves all the tables and fields where my type is used. Then change existing fields to base type - e.g. from `CustID [StringID]` to `CustID [nvarchar(20)]`.
Drop the user type and recreate it with new type - e.g. `nvarchar(50)`
and finally set back fields to user type

I do not have rules defined on types, so don&#39;t have to drop rules and re-add them.

Any help is appreciated.

Alter user defined type in SQL Server

What datatype should I choose for storing an IP Address in a SQL Server?

By selecting the right datatype would it be easy enough to filter by IP address then?

Datatype for storing ip address in SQL Server

Is it a good idea to index varchar columns only used in LIKE opertations? From what I can read from query analytics I get from the following query:

    SELECT * FROM ClientUsers WHERE Email LIKE &#39;%niels@bosmainter%&#39;

I get an &quot;Estimated subtree cost&quot; of 0.38 without any index and 0.14 with an index. Is this a good metric to use for anlayzing if a query has been optimized with an index?

SQL Server: Index columns used in like?

I&#39;m trying to flip a bit field in SQL Server using an update query, that is, I want to make all the 0&#39;s into 1&#39;s and vice versa. What&#39;s the most elegant solution? 

There doesn&#39;t seem to be a bitwise NOT operator in T-SQL (unless I&#39;m missing something obvious) and I haven&#39;t been able to find any other way of performing the update.


How to flip bit fields in T-SQL?

This is a follow-on question from the one I asked [here][1].

Can constraints in a DB have the same name?

Say I have:

    CREATE TABLE Employer
    (
        EmployerCode    VARCHAR(20)    PRIMARY KEY,
        Address         VARCHAR(100)   NULL
    )


    CREATE TABLE Employee
    (
        EmployeeID      INT            PRIMARY KEY,
        EmployerCode    VARCHAR(20)    NOT NULL,
        CONSTRAINT employer_code_fk FOREIGN KEY (EmployerCode) REFERENCES Employer
    )


    CREATE TABLE BankAccount
    (
        BankAccountID   INT            PRIMARY KEY,
        EmployerCode    VARCHAR(20)    NOT NULL,
        Amount          MONEY          NOT NULL,
        CONSTRAINT employer_code_fk FOREIGN KEY (EmployerCode) REFERENCES Employer
    )

Is this allowable? Does it depend on the DBMS (I&#39;m on SQL Server 2005)? If it is not allowable, does anyone have any suggestions on how to work around it?


  [1]: https://stackoverflow.com/questions/1397440/

Content Type	Original Author	Original Content on Stackoverflow
Question	Andrew Shepherd	View Question on Stackoverflow
Solution 1 - Sql Server	x2.	View Answer on Stackoverflow
Solution 2 - Sql Server	Av Pinzur	View Answer on Stackoverflow

How to stop SQLServer writing extraneous stuff eg (1 rows affected)

Sql Server Problem Overview

Sql Server Solutions

Solution 1 - Sql Server

Solution 2 - Sql Server

How to detect when application terminates?

Distinguishing between delegation, composition and aggregation (Java OO Design)

Attributions