Maddave (4/7/2015)

---

Thanks. I agree there are definitely some improvements that could be made with this design.

Unfortunately, I cannot implement the delete by hour, well not yet anyway. The machines...

I hate delete operations. I always feel deletes, especially bulk deletes, indicate something is wrong with the database model or ETL design. What I mean by that is: why insert...

If you have some slush money left over in your disaster recovery planning budget, you can play off the fear of executive management by blocking off an entire day to...

Geo-replication and geo-backups are two different things. Every cloud data vendor should have daily or weekly off-site backups that include even the lowest tier customers who arn't paying for geo-replicatation.

tomsharp85 (4/3/2015)

---

Create Table for CompanyAddress1

...

I don't think an insert into the names is relevant here.Also I thought of splitting the address tables into 3 as in total there are more...

As a side note, without a constraint on this VarChar "date" column it will be a constant struggle to get users to enter data consistently and any conversion functions you...

tomsharp85 (4/3/2015)

---

OK, the names table was a generic way of listing for brevity, the tables are different industry sectors. Yes all of those tables are exactly the same. will your...

Somewhere in the bowls of every large corporation and government agency, there is at least one gray haired person dedicated to doing this....

The total number of pages on a report a user wants to scan through hasn't changed in five years. However, there are scenarios where an oranization prints 1,000 page reports...

My understanding is that you have a Names table, and then you have an Address table. Actually you have multiple Names tables for some reason, but we'll put that aside....

It seems that most public software engineering discussions revolve around the paradigm of either eCommerce shopping carts or social media. But that's just not applicable to most database applications. They...

cyanes (4/1/2015)

---

I have a basic load proc (loading a staging area.) that truncates a target table just before inserting fresh data in said table, all wrapped in a distributed transaction....

LOL! Every SQL Server related job I've ever had, at some point during the first week, I get handed some pile of nonsense like this and told it's now one...

Or when rolling off to history hourly:

where datediff( hour, PrintDate, getdate() ) > 120;

Could it all be as simple this: a single delete operation that leverages an output clause to insert deleted rows into a history table? If this were to be...