from memory, (forgive the pun) Windows 2003 server Enterprise shouldnt need a /PAE switch.

GilaMonster (7/14/2008)

---

that's the thing that worried me, how can public ip's...

check this link

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1721211&SiteID=1

it may be of some use

are you sure you wanteed to audit all tables, that is quite an overhead to place on the database.

installing sql2005 express should be no more than if you were installing another sql2000 instance.

Install a named instance and then remove it when you're done if you want to

i'm assuming he got it from here

TRACEY (7/12/2008)

---

When using profiler. Example

Trying to determine what the measurements are in profiler in MG and GIG

Divide by...

especially the folder permissions, that applies to SQL whether clustered or not

DKG (7/12/2008)

---

[font="Verdana"]Steve, First of all thanks a lot for this excellent explanation.

As per my understanding log file contains uncommitted transactions only, the transaction which is already committed has gone to...

are you using redundant HBA's? It would be advisable

change this

create proc procname

@subject1 int,

@subject2 int,

@subject3 int,

@result int output

as

set @result = @subject1+@subject2+@subject3

to this

create proc procname

@subject1 int,

@subject2 int,

@subject3 int,

as

declare @result int

set @result = @subject1+@subject2+@subject3

it will only expect 3...

are you using a static or dynamic IP address for the windows 2003 server

the [] are commonly used to negate SQL keywords.

say you had a column in a table called object_id, to reference it as a column and not a keyword is like...

this link covers logon triggers

http://technet.microsoft.com/en-us/library/bb326598.aspx

you could have the trigger check the client_host event data using the eventdata function for a known set of addresses and deny logon that way!

of course...

do you mean deploy a database using a windows form or deploying sql server express using a windows form?

to attach the database, copy the files to the desitred location and use the following T-SQL

sp_attach_db 'dbname', 'drive:\path\filename.mdf', 'drive:\path\fiilename_log.ldf'