Viewing 15 posts - 1 through 15 (of 16 total)
Cath Trimble (10/7/2008)
Did you copy and paste Miguel's query? If so there's a typo - it should be sp_change_users_login 'Report' the 'c' was missing from 'change'. ...
October 7, 2008 at 7:25 am
shine.mm (10/6/2008)
hi,this is working but iam not sure the exact result is coming up.
When you run the stored proc on one of the DBs, what's the output you are getting?
October 6, 2008 at 10:42 pm
Steve Jones - Editor (10/6/2008)
October 6, 2008 at 11:30 am
Richard Gardner (10/6/2008)
When building a data architecture you have to consider the front end, the bouncers, as you call them.
You need...
October 6, 2008 at 11:20 am
I strongly dissagree here -maybe because I am taking this quote slightly out of context, but I still like a healthy debate:
Those of us that work with data tend to...
October 6, 2008 at 10:01 am
You should be able to work this out with a little cursor (yack!) to execute and dump results for every DB on the server. Use this system stored proc like...
October 6, 2008 at 9:38 am
Run the following on each DB you restored on your test server:
sp_change_users_login 'report'
Any rows coming back are orphaned users you have on those DBs. If the users coming back are...
October 6, 2008 at 9:14 am
Mike Levan (6/10/2008)
June 10, 2008 at 12:47 pm
Mike Levan (6/10/2008)
Actually its an old system running which...
June 10, 2008 at 11:48 am
Start looking at the statements that cause blocking. This is a handy script I've used in some ocassions -since tracing was not an option.
SET NOCOUNT OFF
DECLARE @blk_spid as int
DECLARE @blk_sqlhandle...
April 23, 2008 at 3:55 pm
Thanks Jack! Well, the solution turned out to be quite simple -though probably not optimal.
Like you said, I can EXEC a stored procedure remotely via a linked server -just make...
April 10, 2008 at 2:12 pm
Similar situation here....any references outside of Quest's knowledgebase -which I can't login to, since I don't know who within the company registered Litespeed?
April 1, 2008 at 3:40 pm
Jeff Moden (3/5/2008)
March 5, 2008 at 9:24 am
Definitely an ingenious solution; however, it can quickly become a poor approach when having to deal with larger import file -think telephone call records for instance.
I've found that the best...
March 5, 2008 at 8:52 am
Adam, the problem was that I was referencing fields by using [remoteserver].[db].[owner].
.[field] and MSSQL wasn't liking it. All I had to do was alias the [remoteserver].[db].[owner] as [aliasname].
In other words,...
January 17, 2008 at 2:41 pm
Viewing 15 posts - 1 through 15 (of 16 total)