Viewing 15 posts - 136 through 150 (of 186 total)
Hi Bouzahme
There may be other ways, but browse to your SQL Log directory (default C:\Program Files\Microsoft SQL Server\MSSQL\LOG) and open SQLAGENT.OUT. You should see a line like this '2007-09-18 08:33:56...
September 18, 2007 at 7:31 am
Hi,
When you run the job from the command line it's running under the login credentials you used to log into the server. When the job is run by the Agent...
September 6, 2007 at 6:30 am
Hi Ammad,
The Reportuser user in the restored database has been orphaned. This link should tell you all you need to do to fix it:
http://vyaskn.tripod.com/troubleshooting_orphan_users.htm
Cath
September 3, 2007 at 1:40 am
Hi,
Your log restore sequence is being broken somehow. Double check all the times and durations for your scheduled backups, copies and restores, make sure they all have time to complete...
August 31, 2007 at 3:22 am
Hi Kevin,
In Management Studio browse to Security\Logins. Right click over the login you want to script and select Script Login As.. Create to...
Cath
August 30, 2007 at 6:38 am
Hi Amit,
When you run the job yourself, it runs under your login, which has permissions to write to your drive. When you schedule the job, it's running under the SQL...
August 14, 2007 at 2:01 am
Hi,
Are you pinging the server by IP address or by FQDN? If you can't ping by FQDN there could be a problem with DNS.
Cath
August 8, 2007 at 8:30 am
Hi Bart,
Disibuted Transaction Coordinator is a Windows Service - you already have it. This should explain more:
http://msdn2.microsoft.com/en-us/library/ms681291.aspx
Cath
August 3, 2007 at 2:03 am
Hi Slowjoe,
Check the collation for both servers, it sounds like one of them could be case-sensitive. If you right click over the instance in EM and select properties you'll see...
July 31, 2007 at 3:42 am
Just a thought – check the schedules on your backup, copy and restore jobs. I had to allow some latency in mine to give the servers enough time...
July 6, 2007 at 7:59 am
Hi Tom,
I had a similar problem - copies/restores were reporting success on the secondary server, but the monitor was sending out failure alerts. For me it was a DNS issue...
July 6, 2007 at 1:51 am
Sergiy, it was actually you who took this thread off-topic. In the first paragraph of the first post to this thread David wrote:
"If you think banker's rounding is stupid, we...
June 29, 2007 at 1:47 am
Cheers Chris, you're right of course. David, David, Noel, Lynn et al are doing a sterling job in the face of adversity. Their patience and perseverence are a shining example...
June 28, 2007 at 6:07 am
I've been watching this thread from the start and have learned some interesting stuff about mathematics, so thank-you everyone for that.
However, anyone thinking of joining...
June 28, 2007 at 2:18 am
It could be that the user has been orphaned - happens when the database is moved to a different server. Try this command:
Use mydb go sp_change_users_login 'report'
then this on the login...
February 22, 2007 at 1:42 am
Viewing 15 posts - 136 through 150 (of 186 total)