A .sql file is a sql script which in your case probably is used to create the database.

You can open it with a SQL Server client like Management Studio or...

Sorry Peter to correct you but nvarchar too is 8000 bytes, but the length is limited...

Since you don't want to use maintenance plans I assume you use your own scripts. To define the retention period just use the RETAINDAYS option.

Something like:

BACKUP DATABASE pubs TO DISK='C:\Backup\pub.bak'...

Could you explain a bit more what you mean by security level?

IF you're looking at db_roles, they are the same.

On server level some new permissions are introduced, mainly to...

Where do you get this information from?

This little test shows that a variable can hold more than 4K

DECLARE @var char(8000)

SET @var = (SELECT REPLICATE('Test',2000))

SELECT @var

Markus

Operating system error 5 means either the path does not exist, a file with the same name already exists or access is denied. So check the path and the filename...

No,

Datareader only has Select permission on all tables and views.

Unfortunately there's no such role as ExecuteAll, you have to create your own db_role.

What kind of scripts are you talking about?

How do you execute them?

Are they containg hardcoded servernames or what exactly is your problem?

Of course when you use a different...

A Login is a server object has no Schema. Only a database user has a default schema.

SO

Create Login user1 with password = '123xTYU'

--Creates a login, but no database access

USE...

Stephan,

NO you can't do an in-place upgrade from 32-bit to 64.What you can do is install a 64- bit instance next to your existing 32-bit instance and then dettach the...

In SQL 2000:

In the Serverproperties enable Login auditing for succesfull logins (or all). Then all logins will be to logged and you can query the SQL Errorlogs.

Under SQL2005 with SP2...

Would this be what you're looking for ?

select ROUND(ROUND(277760/12*31,0)/10000,0)*100

Not really sure what is going on but you're right the datalength function should return the actual bytelength.

But you also mention the use of merge replication. I'm know for...

Sorry, I don't have a ready made script but if you query msdb.. backupset and msdb..nbackupfile you can find all the information you need.

Sounds like your column(s) is defined as a nvarchar which takes two bytes of storage for each character.

Markus