Do you have an installation of SQL Server as a server somewhere?

noeld has a great solution, which I wish I'd thought of.

On the subscriber you'll have two tables that represent your indexed views. create a view over them.

select a.1, a.2, a.3,...

Well I thought that was a new one, but it seemed interesting with the update from the OP.

Definitely some creativity at work there.

The issue you'll have is that this isn't a one time thing. With replication, the "tables" will be changing constantly.

The easy way would be to insert from one table, and...

Where is the empty password? I can fix that. I don't see one in the code for the article.

I'd still vote for 13 separate databases, and turn Barry's comment around. It's harder than one database, but not 13x harder. Just a little harder.

Please do not post your question in the title.

Post the details, version, and issue here in the thread.

Any of the basic books on SQL Server 2005 contain general information. One is as good as another. I'd recommend Brian Knight's admin books because he's a friend and they're...

We have 3 dbs on the site here. One runs 2005 in 80 mode, the others are 90. We are looking at 2008, but it's mostly a PR thing, not...

Hint taken, it's on the list.

you absolutely need indexes, but minimize the number of them.

Paritioning can help if you have some basis for partitioning (times, IDs, something).

You might consider using a second table that summarizes...

closing

The tool is from the SQLCAT team at Microsoft, and if you follow the link (http://sqlcat.codeplex.com/Wiki/View.aspx?title=ExtendedEventsWaitstats), it says for 2008.

If you have more questions, I'd contact the SQLCAT team.

Tony is off today, but he should respond tomorrow.

I agree we want to write code correctly the first time, but there will always be bad code. Always new people, always...

I think Excel is great in single sheets, or maybe a couple simple links.

Once you start to go beyond that, it can become a huge mess. I spent months untangling...