Take a look at the undocumented procedure sp_MSforeachdb. It will do exactly what you are looking for.

My boss is very weak when it comes to anything SQL. In fact he insisted that my Customer table have two fields that I thought should have been in another...

First of all welcome. Great job posting some consumable data and information.

You have a couple issues with this. You can't convert your string formula to float. That is no...

Selahattin SADOGLU (9/8/2011)

---

Hi Folks,

I have some issues with stored procedure on SQL Server 2005.

My Conditions:

1-by date range,

2-according to cari_kod,

3-according to stok_kod,

...

Replication. It sounds like it is exactly what you are looking for.

You would need to group by all your columns. You can't do an aggregate function if you don't specify what to group by. If the reason you don't want all...

ashok.faridabad1984 (9/7/2011)

---

Hi,

However there is no harm in having separate column for type and moreever you can have fix length of ID like xxyyyyyyyy where xx can be your type,...

And converting to utc for historical data gets really complicated if you need it exact due to the daylight saving time changes made in some sections of certain timezones. International...

That will work if all the users are in the same timezone as the server. Otherwise you will have to determine which timezone they are in.

Good point about the...

So then I for any change, it'd just be a matter of doing a SELECT on the table with the next lowest primary key than the record being viewed as...

You would have to know what their time zone offset is from gmt. Then it is just a dateadd.

If the user's timezone is -6gmt then just dateadd(hh, -6, DateField)

david.holley (9/6/2011)

---

Sean Lange (9/6/2011)

---

These are the exact challenges I was suggesting you would run into in your original thread about these auditing triggers. It is challenging to put these records...

fyi, the text and ntext datatypes are deprecated. You should instead use varchar(max) or nvarchar(max).

These are the exact challenges I was suggesting you would run into in your original thread about these auditing triggers. It is challenging to put these records back together so...

@@ROWCOUNT just says how many rows were affected by the last sql statement. So when you try to insert...if @@ROWCOUNT = 0 you need to insert from your second statement....