No No No. Check out STUFF in the BOL.

SELECT STUFF('abcdefghijkl', 6, 0, '1234')

This says: STUFF the expression 1234 into abcdefghijkl starting at the 6th position and delete 0 characters.

-SQLBill

Changing it is no problem. Just remember to schedule transaction log backups. (And 5.25 GB isn't a large database in SQL Server - my main database is currently over...

My opinion:

use the format of yyyy-mm-dd for inputting dates into the database. That format is always understood by SQL Server. dd-mm-yyyy or mm-dd-yyyy can be misunderstood by SQL...

You really need to read the BOL on doing backups. But......

Let's set up a job to backup the master database to disk......

first you create a 'dump device':

USE Master

EXEC sp_addumpdevice 'disk',...

Are you sure the database finished loading? How long did it take to make the backup and how long has the restore gone on?

You might try running just:

RESTORE DATABASE dbname

WITH...

That's why it's best to keep your stats updated. In the BOL, look up sp_updatestats and UPDATE STATISTICS commands.

-SQLBill

It is always a good idea or best practice to use the full naming convention (or most of it).

Try.......

EXEC dbo.sp_OACreate

-SQLBill

DBAs with local admin access to the SQL Server box. Speaking as a DBA, no it's not really necessary. HOWEVER, that means we can't install updates, patches, etc. ...

There is one way.......create an UPDATE trigger that returns the date and time to a file. It can also return the row that got updated if that's what you need...

I create manual backup plans and schedule them as jobs.

For example, I have one job called Full Backups. Each step in that job does a full backup of one of...

Which version do you have?

Run this:

SELECT ServerProperty('Edition'),

ServerProperty('ProductLevel'),

ServerProperty('ProductVersion')

-SQLBill

Dave,

It usually means that a column is too small for the data it is receiving.

For example:

MyTable

MyCol CHAR(5)

INSERT INTO MyTable (MyCol)

VALUES ('123456')

That will fail since I am trying to...

Also, I don't believe VARCHAR(MAX) is valid TSQL syntax.

MAX in TSQL requires an expression that if finds the MAX of. MAX(MyDate).

-SQLBill

Max length of NVARCHAR is 4000.

Max length of VARCHAR is 8000.

@Message is of NVARCHAR data type.

-SQLBill

Is the server using Mixed Mode authentication or Windows Only? If it's set for Windows Only, then the SA login is disabled.

-SQLBill