This is one way of doing it,...

Or you can install the client components on your desktop computer. This has the following advantages:

(1) You're not logged on to the server and stopping someone who needs to...

As Muthukumaran suggests, it may turn out that your only option is to get a bigger disk. This is because your log file needs to have at least enough...

It might be worth setting minumum server memory as well. That way, if anything is trying to grab memory back, it won't be able to. Also, are you...

Why do you say there'll be a performance loss on commit if the log is getting cleared (of inactive portions only) on a checkpoint?

Got some tests that show the performance...

I can't find where it says that in SQL Server 2005 Books Online. I have the April 2006 edition. The closest I can find is the following:

If you...

I usually move them to different drives. There isn't any great dogma behind this - it's just that since I have data files on one drive and log files...

Our system drives are often created with very little spare space by the people who build the servers. We usually have no choice but to move the system database...

Two reasons I've seen for not being able to start SQL Server Agent:

(1) The location specified for the SQLAGENT.OUT log file is incorrect or the permissions on the location are...

Thanks for the article, Jimmy. One thing you might want to consider is that if you have large data files with small amounts of data in them, backup and...

Yes, and then revoke access for all the users on all objects except the procs and views, so that the users don't continue to run the old queries.

John

Start with a query something like this:

SELECT

TABLE_SCHEMA + '.' + TABLE_NAME AS [Table]

, COLUMN_NAME AS [Column]

, DATA_TYPE + COALESCE('('+CAST(CHARACTER_MAXIMUM_LENGTH AS varchar(4))+')','') AS [Data Type]

FROM

INFORMATION_SCHEMA.COLUMNS

ORDER BY

...

Interesting behaviour. If you change the last SET line to SET @msg = @msg+@msg+@msg then you get 111111 (at least you do with SQL Server 2005 SP3). Strange...

(2) View the data? What if you want to modify it?

(3) That's interesting - I've never used it. Does it include foreign key constraints?

(4) So the numbers are...

(1) Security. You can only have one password per spreadsheet, instead of one per user. And Excel passwords are very easy to crack.

(2) Concurrency. It's much easier...