Search results

  1. A

    Database log file is full

    One solution that I can think of is to perform A LOT of small operations like inserting or deleting a record. This should free some space in the log.
  2. A

    Database log file is full

    Good question. Since you're not a member of db_backupoperator or db_owner, you can't use DBCC SHRINKDATABASE or BACKUP. I just hope the SQL Server is configured to truncate the log on checkpoints by default (you can't change this option yourself too :) ), then it will be freed after "some time".
  3. A

    Can't connect to mssql4

    Argh! Stupid me! I did not check the protocol - I was trying to connect with Named pipes instead of TCP/IP. Changed it to TCP/IP - now it's OK. :)
  4. A

    Can't connect to mssql4

    No, I have a direct connection. I will play with client tools' configuration and will let you know the result.
  5. A

    Can't connect to mssql4

    I created a new MS SQL DB (it says it's on mssql4) and I can't connect to it with Enterprise Manager or Query Analyzer. They say "SQL Server does not exist or access denied". Tried to put IP instead of the hostname as Yash suggested - all the same. I doublechecked the login/password so I'm sure...
Back
Top