Here is the build script:

CREATE TABLE [dbo].[item](

[item_urn] [int] NOT NULL,

[cat_urn] [int] NOT NULL,

[item_mnc] [varchar](10) NOT NULL,

[item_descr] [varchar](50) NULL,

[item_active] [char](1) NULL,

[item_device] [varchar](20) NULL,

[item_type] [char](1) NULL,

[dept_urn] [int] NULL,

[modified_by] [varchar](16) NULL,

[mod_timestamp] [datetime] NULL,

[mnc_descr_mod]...

Good reply! You are right I should put in a minimum page count. Still annoying that it is taking so long. I would of said the same...

Is level 8 published anywhere?

Found those as well 🙂

Using those to validate and flush out my points.

This presentation is going to be brutal for the listeners if I don't clean it up...

Thanks Gail 🙂

I had found that on my hunt for more information...I am actually doing a presentation on the T-LOG...

Per Sean McCown, I purposefully selected a rough topic...

Just got back from a little walk and that is what I was thinking Gail (not the smart stuff, but that BoL is probably under stating the conditions)...

Oh well...

I will...

Found this on books online:

Transactional Replication and the Transaction Log

If a database includes one or more transactional publications, the log is not truncated until all transactions relevant to the publications...

Is it possible that they have multiple per one day? You are counting distinct days. Why not just do COUNT(*).

What duplicates are you trying to rid yourself of?

Not pretty, but it seems to work for me:

I created the following table to help with data type declaration:

declare @DataTypeVariable table

(

name varchar(30),

system_type_id int,

user_type_id int,

max_length char(1),

precision char(1),

scale char(1),

primary key (system_type_id,...

Not sure it is a good idea, but my way around this is by creating a table with every data type to get the defaults. Then do a comparison...

Fantastic thanks for the feedback!

Is it safe to put a delete switch in as well?

CREATE TABLE TestTable (id TINYINT PRIMARY KEY IDENTITY(1,1), name NVARCHAR(10));

INSERT INTO TestTable (name) VALUES ('a')

GO

CREATE PROCEDURE SaveTestTable @id TINYINT, @name...

I think you answered my question. I have never used the term "upsert", but that is exactly what I am doing.

"Generic Save" was the only thing I could come...

These seems to work, but I am getting different results when linked servers are involved...

create table #t (a varchar(10))

declare @sql nvarchar(max) = '';

begin try

set @sql =...

Why I am always so excited to find stuff to post here.

The feedback really is amazing stuff!