That's a really strange requirement, since generally you don't have the same tables in every database. It's possible, however, but it would have to be done through dynammic sql....

It is definitely possible. Best practice may dictate creating a table specifically for it, but I can't say for certain. Personally, I've always placed universal functions/procedures in the...

Personally, I've always used user-defined scalar functions to return the first day of the year or quarter for a given date.

Example:

CREATE FUNCTION fn_DATE_FirstDayOfYear

(@date DATETIME)

RETURNS DATETIME

AS

RETURN DATEADD(yy,...

Well, ultimately breaking it into blocks gives me complete control over the transaction log size. In this specific case, disk space is more important than performance. I can...

I had trouble removing the clustered index on InvoicedDate (it was taking a long time), but I was finally able to do it. I tested the stored procedure with...

Lynn Pettis (4/19/2010)

---

I wrote a set of procedures for a previous employer that dropped and recreated the indexes and foreign key references on specified tables that were used before and...

Lynn Pettis (4/19/2010)

---

Here is a guess at why you see a larger growth from stage to production than from source to stage: indexes on the production table(s). Do you...

The easiest way seems to be looping based on an identity key. I've broken up the transaction into groups of 50,000 rows, and a CHECKPOINT is issued manually (just...

I'm confused as to how BCP or BULK INSERT would help, considering the data...

Danny Sheridan (4/19/2010)

---

I had a similar issue in our production environment where our transaction log was growing to unacceptable sizes after bulk data loads. In my case, the transaction...

Lynn Pettis (4/19/2010)

---

All of this:

The first INSERT statement moves about 800,000 rows from these tables. The second INSERT statement creates about 200,000 rows in the fact table by querying the...