No you won't lose data b/c only active portion of the transaction log is

backed up by SQL Server

MW

Edited by - mworku on 06/12/2003 6:32:19 PM

You can script all of them in one file and just do search and replace

MW

If you're worried about conflicting locks try changing the value for LOCK_TIMEOUT system var. If your procs are not involved in data modification and data being read is small,

all shared...

Got lost with the logic b/c of all the wordings,

Give an example of your table structure and a sample query

MW

I Can't really understand your question.

Give more details and query examples

MW

Try changing your client Net Lib to Named Pipes

MW

Edited by - mworku on 06/11/2003 8:34:40 PM

Try using the server's IP address

MW

You can use the (env) command to list all system and user environment

variables. The findstr command will filter out just those vriables

with the word SQL_BACKUP and you redirect the output...

If you do all error checking within your T-SQL script, you can create

multiple procs. one for each job. After that all you have to do is call your

main proc let...

In EM expand

1. Replication Monitor

2. then expand Publisher

3. expand the Publishing Server Name

4. click on the database you want

5. from right window pane right click on the snapshot icon...

You would see a performance gain if you put your data processing logic

in a stored proc. After the initial execution the Stored proc. is cached and SQL server

uses a pre-compiled...

Select Convert(varchar(30), GetDate(), 103) will format date to dd/mm/yy and

If you need the time value you need to use concatenation

Select Convert(varchar(30), GetDate(), 103)+' '+

...

You can use user defined role and add members to the role.

Whatever permission the role is given will be inherited by members.

But every time new objects are added, you need...

The correct expression is (OR), if you use (AND) you'll end up with courses that are

active and courses that begin with 10 only.

This reply by jpipes works if you change...

Make sure you're executing the proc. under the mater DB context

I recommend fully qualified names

Ex. Exec Master..xp_cmdshell 'c:\test.vbs'

MW