Is your SQL Server set up for Windows Only or mixed authentication?

Is your login set up for Windows only or SQL Server only?

-SQLBill

Bill,

Two issues.

1. The TEMPDB is growing huge. There are two usual causes of this. First, you have some huge transaction occuring or are doing database maintenance. Second, you have your...

1. You must have a login on SQL Server that is set for Windows Authentication only.

2. The login must be the same that you use to log into the network.

3....

I don't use SQL Server 2005, but some checking with SQL Server 2000 shows there is an option with sp_configure that sets the remote access (option name is "remote access")....

There are several things that can cause a transaction log to grow to huge amounts (yes, larger than the database itself). Mostly, reindexing or defragging the indexes will cause...

So, did you check your settings on the SQL Server to see if it allows remote connections?

-SQLBill

You run this:

declare @dSTART_DATE datetime

declare @Time datetime

set @dStart_Date= getdate()

Set @Time = '08:26:00'

SELECT CONVERT(VARCHAR(10),@dSTART_DATE,101) + ' ' + convert(varchar(10),@Time,108)

and get the error. Of course you do...you are trying to convert...

BTW-If you get a 0 (zero) returned, it means there are values that are not dates. If you get a 1 (one) then all values are dates.

If the 0...

Are you sure all your values ARE dates? Run this:

SELECT ISDATE(d_StartDate)

FROM tablename

-SQLBill

No problems with that, except for the fact that from there you want to convert it back to datetime. SQL Server doesn't know what 01/27/2006 equates to. Is...

Why do you want to drop the database?

EM might have taken longer to open because when you stopped the process it had to rollback the transaction. The amount of...

DBO is a reserved word for DataBase Owner. It cannot be a user created login or role and cannot be mapped in the way you want to do. ...

BTW-I would suggest putting your date in the yyyymmdd format (use 112 vice 101).

-SQLBill

You don't give us any sample values for @dSTART_DATE or @Time. So run this, using your values, and show us what the result is:

SELECT CONVERT(VARCHAR(10),@dSTART_DATE,101) + '' + convert(varchar(10),@Time,108)

-SQLBill

Removing the @txntime is the best option UNLESS you may have to enter that value.

Other options:

Change the order of the parameters when you create the procedure:

PROCEDURE add_dependent

@FName varchar(50),

@MI char(1),

@lname...