The only time I can think of when a PK would be optional is when the entire table will fit onto one page. And, even then I'd probably create one...

Tables involved in replication need at least one uniqueidentifier column. If you don't have such a column one will be provided for you.

'sokay - you can't drive me someplace that I already am!

Additional processor could help. Don't know what you're using for disk storage but...

That's the spirit! I'm pretty certain that the view to emulate what you have now would be quite tricky, though you may be able to replace some of the CASE...

Yes, I am suggesting that the more complex calculations be moved out of the triggers and into the retrieval process. Fundamental design rule: do as little as possible in time-sensitive...

I may be totally off base, but IMHO you really have only one option: ditch the complicated triggers. Your performance issues are (by your own admission) due to a complex...

Well, at least not their Marketing Dept. LOL!

Steve G.

I think the one thing you can get out of this thread is that there isn't a simple answer to this question. How big the transaction log gets depends on...

Use Access. It's not the greatest solution in the world, but it does work - IF the table/view does allow you write access. Which brings up the larger issue of...

Sounds good - though 10 seconds would be a really long query. 😉

There are many other things that can slow down performance, especially tables with large numbers of indexes that...

This is not necessarily a problem. The t-log size is (as was stated above) a reflection of the amount of change activity on the database. A small database with a...

Why do you think this is too large? Are you running out of disk space? If you aren't then leave the t-log size alone. Since it's just continuing to grow...

After I do a database back up one of the primaries, the next log file backup is large - so I do full DB backups 'round midnight when nobody cares...

The databases on your secondary server *are* a backup of your primary databases. There's no need to back up your backup. FWIW, the databases on the secondary server are not...

You could try a simpler option.

Create a third table that has only an identity column. Change each of the two tables to have a foreign key relationship with the third...