Viewing 15 posts - 1,306 through 1,320 (of 1,654 total)
Todd,
Sounds like the two servers are having a different collation. When you create a linked server you can set some options like which collation the linked server should use (remote,...
[font="Verdana"]Markus Bohse[/font]
April 23, 2007 at 8:53 am
Trigger,
SQL 2005 maintenace plans are actually SSIS packages stored in the msdb database.That's the reason you get this error. Anyhow the job history should help you identifiying the error.
Markus
[font="Verdana"]Markus Bohse[/font]
April 20, 2007 at 3:40 am
This gives you the name of the filegroup, the logical filename and the path.
SELECT fg.Groupname, f.Name, f.filename
FROM sysfiles f JOIN
Sysfilegroups fg
ON f.groupid = fg.groupid
In SQL 2005 you...
[font="Verdana"]Markus Bohse[/font]
April 20, 2007 at 3:21 am
Dean,
if your named instance uses a fixed port you can define an alias on the client. In that case the client don't need to query the UDP port.
Markus
[font="Verdana"]Markus Bohse[/font]
April 20, 2007 at 12:48 am
Dean,
the SQL Browser service is new in 2005 and as far as I know it won't effect SQL 2000 instances.
Did you try creating an alias for your instance?
Markus
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 5:55 am
For tables and view you can use this query:
select o.name, xtype
from sysobjects o
WHERE id in (Select id from syscolumns where name ='column_name')
For stored procedures and functions you can then run...
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 5:45 am
Best point to start investigating any job failures is always the jobhistory.
Right click your job and select view history. Usually it will give you the reason why a job failed.
Markus
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 4:25 am
Jacques,
I've seen similar issues in the past and most of the time the reason for the failed logins is that either in the datasource or hte connection string the process...
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 4:23 am
Gurvinder,
I'm not aware of any standard solutin for this problem. You might be able to scripts something which checks on a regular bases for proces id -2 and when looks...
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 1:06 am
Hi cmt,
I can't see you error message but I suspect that your time-out is caused by the client and not SQL Server. SQL Server actually doesn't have a query timeout...
[font="Verdana"]Markus Bohse[/font]
April 18, 2007 at 9:02 am
A process ID of -2 indicates an orphaned connection. In order to kill it you need to look up it's unit of work (UOW) id from the syslocks table and...
[font="Verdana"]Markus Bohse[/font]
April 18, 2007 at 8:55 am
I've had the same problem on a couple of servers.
As you already noticed the instcat.sql script will basically recreate almost all objects in the master database. In my case we...
[font="Verdana"]Markus Bohse[/font]
April 16, 2007 at 6:58 am
Dana,
the first thing I would check is if the service for reporting services is installed.If that's the case, when probably RS has not been configured yet. To do that, open...
[font="Verdana"]Markus Bohse[/font]
April 16, 2007 at 6:51 am
Matt,
I'm not sure where you are looking but if you open "Job activity monitor" under SQL agent you should see all the information you are looking for.
Markus
[font="Verdana"]Markus Bohse[/font]
April 16, 2007 at 6:44 am
[font="Verdana"]Markus Bohse[/font]
April 12, 2007 at 11:15 am
Viewing 15 posts - 1,306 through 1,320 (of 1,654 total)