Here's a weird idea, start worrying about it when you plan to move to sql 201? and having the upgrade advisor throwing errors and warnings.

In the mean time...

Ya but she looks...

Yup... but only use in this case. When manipulating names and adresses you can get in trouble. But in this case the only trouble would be to have...

An even more important question than what is being used...

why more to SSRS in the first place? What's so wrong with B.O. that you will be able to fix...

wow you guys like to work hard!!!

DECLARE @str VARCHAR(250)

DECLARE @name VARCHAR(250)

set @str = '\\IP_Address\DirName\DirName\DirName\twProcessDB_20100819173001.trn'

SET @name = RIGHT(@str, CHARINDEX('\', reverse(@str), 1) - 1)

SELECT @name, REPLACE(@str, @name, '')

:w00t::cool::hehe:

Yup, anything you need the last of something that's a really good way to go :hehe:.

DECLARE @str VARCHAR(250)

set @str = '\\IP_Address\DirName\DirName\DirName\twProcessDB_20100819173001.trn'

SELECT RIGHT(@str, CHARINDEX('\', reverse(@str), 1) - 1)

Well then that should be your best bet. List all the reports, make some "help" file and present to all users at once. Then at the end of...

From my experience cleanup is often a bit of a waste of time (unless done right after dev). However here's the way to keep your history for longer :...

Here's a very crud way for solving the problem once in a while.

exec sp_who2

Look at the blocked by column. That will list the spid that is most likely blocking...

The only thing I can think of is that by default, profiler excludes its own application name.

So you may get different results by removing that filter from the 2nd trace...

Moreover the only we saw to enforce that license was to host the reports on our own servers in our building. But that comes with a host of major...

I see your point. My questions was strickly refferring to building a bundle of reports that we then sell as a package to a client.

In that case we grant...

It won't really. The only different it'll make is that now the report is on the web server rather than report server. Still the source is freely available...

Something like this should do the trick.

SELECT COUNT(dtCnts.*) As NbApplications, dtCnts.CntContacts FROM (

SELECT ApplNbr, COUNT(*) As CntContacts FROM dbo.Contacts GROUP BY ApplNbr

) dtCnts