Forum Replies Created

Viewing 15 posts - 1,306 through 1,320 (of 1,655 total)

  • RE: Cluster failover notification

    Adam,

    with "SELECT SERVERPROPERTY('ComputerNamePhysicalNetbios') you can query on which clusternode SQL Server is running.

    You could then create a job which is scheduled to run when SQL Agent starts. During failover...

  • RE: What could be the difference?

    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,...

  • RE: Backup Mayhem

    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

  • RE: Filegroups in SQL Server 2000

    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...

  • RE: SQL Server instances not reporting in browser

    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

  • RE: SQL Server instances not reporting in browser

    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

  • RE: Finding where a column name has been used

    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...

  • RE: Jobs in sql server 2005

    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

  • RE: strage error: 18456, Severity: 14, State: 16.

    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...

  • RE: SQL Server 2000 DBCC being blocked by "Process ID -2"

    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...

  • RE: Question regarding TimeOut when for example updating table

    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...

  • RE: SQL Server 2000 DBCC being blocked by "Process ID -2"

    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...

  • RE: 64 bit linked server issue

    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...

  • RE: 2005 reporting services!

    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...

  • RE: SQL 2005 Server Agent Jobs view - want view like SQL 2000

    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

Viewing 15 posts - 1,306 through 1,320 (of 1,655 total)