Gail

I don't know whether this works in SQL Server 2005, but in 2000 you can insert the result of xp_errorlog into a temp table, then query to find the earliest...

PM

You should be able to attach the database.  You have to specify a name - I would guess HA_Raw_38 was probably the original name.  You can find the syntax for...

I think I agree that bitmasks are to be avoided in most instances.  But what happens when the number of bit columns is not known at design time, for example...

Denise

I imagine you'll find plenty of white papers and the like on Microsoft's website.

John

David

The WITH MOVE and WITH REPLACE options are used if you are restoring using T-SQL, for example in Query Analyzer.  Their respective Enterprise Manager equivalents are changing the file names...

Dan

I'm afraid this still doesn't make sense.  You can't have a foreign key constraint in TEAMS referencing the TEAM_NAME column in TEAM_PROFILE since that column does not have a unique...

Ian

There are scripts you can search for on this site for estimating table and database size.

As for log space, this depends less on the size of the database than on...

Dan

This DDL doesn't make sense, for the following reasons:

(1) The syntax for the foreign key constraint in the first table is wrong

(2) You're missing a comma from the second table...

Jo

Just an idea, this...

You have a stored procedure called TEST5 in a database called Statistiek, right?  I've a feeling that EXEC Statistiek.dbo.TEST5 will execute that proc against Statistiek rather than...

Scott

Right click on the database in Enterprise Manager, choose Properties, and click on the Transaction Log tab.  Enter the new value in the Space allocated box and click on OK. ...

Scott

Obviously your log file isn't large enough to accommodate the data from inserting 1000 rows.  So the solution is to make the log bigger and turn off auto shrink.  No...

David

The clue is in the error message.  The database you are restoring from has different file names and/or paths from the one you are restoring to.  So you will need...

I assume the "+" is a typo?  Your query will return all rows from table1 and table2 where the value of the column b in table1 matches the value of...

Scott

A full database backup won't affect the size of your log.  Truncate your log like this:

BACKUP LOG MyDB WITH TRUNCATE_ONLY -- if you don't need to be able to restore

BACKUP...

This won't work if some of your data is (n)varchar or text.  If you want to count the size of these rows individually, you'll need to use the datalength function. ...