SQL does a lot of implicit data type conversions when it is processing queries. This occurs whenever the data types are not exactly the same (e.g. assigning an INT...

You can change the properties when you create the article - you may notice elipses (...) next to the table name. In the same dialog, you should see an...

Sorry - I assumed you were using AS 2005.

For AS 2000, everything is done using Analysis Manager. You should be able to find this in the SQL Server program...

The simplest way is to use the backup command from within Management Studio. Just right click on the database and select backup. You also have the option to...

These stored procs are what replications uses by default for inserting/deleting/updating records on the subscriber. You can change this to use INSERT/DELETE/UPDATE statements if you wish. These are...

There are some really good products on the market that will do exactly what you are trying to achieve. Idera's compliance manager is one such product (there are others...

How about something like (I hope is right - I haven't got access to a SQL Server instance to check it)

DECLARE @yearlist cursor for select distinct year from table_1

DECLARE @EndYear...

You can group by as many columns as you need.

Consider the following

Create table1 (col1 int,

col2 char (10),

col3 char (10),

col4 money)

You can use the following select

SELECT COL1, Col2,...

If the data is not a column (or part of a column) then you simply cannot do it. You need to revisit you data source and add sufficient data...

I am not sure what your issue is wrt the Census and the "housing/income" groups. I would have thought that adding a column group would do exactly what you...

This issue arises because you have an instance of SQL and, by default, when you log onto that server and run Enterprise Manager it uses "local". The replication wizards...

The data you are logging seems (to me) to be very similar to the logs that are kept by reporting services already. Have a look at the table "ExecutionLog"...

The short answer is yes - any extra work (e.g. whatever the trigger does) will slow replication down. If you write efficient code for your trigger, the impact will...

This sounds like a reasonable use of a trigger to me. 50,000 records should be OK (subject to all the usually caveats about other workload on the machine etc,...

No real reason other than separating the logic so that it was obvious - yep, they could be in one select statement