The ideas I've heard, and what has been built into Powerpivot with Sharepoint 2010 integration is a way to watch and see which applications are heavily used and they can...

Great point, Jack. You can also use the UPDATE() function in the trigger to check things. http://msdn.microsoft.com/en-us/library/ms187326%28SQL.90%29.aspx

For anyone else confused, the SQL CLR is a programming platform inside SQL Server that allows you to write your own assemblies in any .NET language to call from t-sQL...

If you are storing these as numerical values you will need to CAST them as strings.

select cast( year as char(4)) + cast( period as char(2)) + '01'

In the future,...

SQL Server will use all the RAM it can based on activity. However, once the activity slows, it does not release that RAM, instead maintaining it's cache for the next...

You can use information_schema.tables and information_schema.columns to get data about the database.

In terms of figuring out what has changed, unless you have a good way to identify changed rows, I'm...

In a trigger you would use the "inserted" virtual table.

update demo

set bemodified = 1

from inserted i

where demo.id = i.id

Be aware that triggers fire once for ALL...

Are these stored in one field or multiple fields?

separate fields, use the + to contatinate values

select year + month + '01'

you don't include the column in the UPDATE, only the SET.

UPDATE dbo.ResourceOwner

SET dbo.ResourceOwner.UserID = dbo.Testupdate.userid

FROM dbo.ResourceOwner INNER JOIN

dbo.TestUpdate ON dbo.ResourceOwner.RESOURCEID = dbo.TestUpdate.EquipId

WHERE (dbo.TestUpdate.EquipName <> 'NULL')

the logic is

SELECT xxx

from EMP

will return a row for every row in the EMP table. If xxx is a column, it returns the values from that column. In your...

Again, it's not you, or the account you use in SSMS. It's the SERVICE account that SQL Server uses that executes things, not any of your accounts.

Anything that makes use of tempdb, especially large transactions that have sorts, index rebuilds set to use tempdb, etc. will cause transactions in tempdb. It is the same as what...

Actually based on this thread I think the most often used words are "urgent" or "start your tests"

😛

Mr Denny and Jeff have given you a good explanation. When you run something in SQL Server, using SSMS or your client, it doesn't run under your windows account, or...

third vote for George here.

If it grows every day, and you shrink it every day to have it grow again, does that not seem silly? What's the point?