I have not seen this issue. I ran a simple test with a fairly long email from Outlook and could read the body in sysmail_allmailitems.

SQL Server is just storing...

SQL Express does not include SQL Server Agent so you can't run jobs from it.

I'd suggest creating a batch file that uses sqlcmd to execute the procedures. You could...

Well, you would use BIDS (Business Intelligence Development Studio) and do a new SSIS project. You'd have at least one DataFlow task that would include a Flat File source...

Pete,

I think the method you mention is the way to go. One thing to keep in mind is that you don't need to add a column tot he table,...

CirquedeSQLeil (1/28/2010)

---

Jack Corbett (1/28/2010)

---

Alvin Ramard (1/28/2010)

---

CirquedeSQLeil (1/28/2010)

---

Today is a Thread Gone Wild day - and I am still catching up.

So will you pay for travel expenses of those denizens that...

Alvin Ramard (1/28/2010)

---

CirquedeSQLeil (1/28/2010)

---

Today is a Thread Gone Wild day - and I am still catching up.

So will you pay for travel expenses of those denizens that are closer (Jack...

Steve Jones - Editor (1/28/2010)

---

I think the biggest issue with SQL Injection is the front ends. It's not SQL. Even if I have a good proc, spDoSomethingCool, if I call...

Dale,

If the OP uses a logon trigger to block SSMS\Query Analyzer and still uses sa then they have locked themselves out from using that tool as well.

Another issue with using...

This actually sort of goes along with the SQL Injection theme and the original theme of the thread. Several Threadheads have already chimed in. It's the thread where...

jcrawf02 (1/28/2010)

---

GilaMonster (1/28/2010)

---

No you're not. There's no concatenation anywhere in that piece of code. Concatenation means...

1. You should NEVER use sa.

2. There is not a simple way to block users from accessing SQL Server using query analyzer or any other application once you...

You can query sys.dm_exec_requests using the session_id (spid) and cross apply to sys.dm_exec_sql_text using the sql_handle.

You definitely would need to change your data sources to reference the correct instance. You could also use DNS Aliases as described by Allen Kinsel here.

How are inserts/updates/deletes being done? Are you using Stored Procedures or Ad Hoc sql in the application? Do you have control over how it is done?

The first thing...

This procedure takes 3 parameters, is_sysadmin, job_owner, and job_id. After some testing, it appears that you must be sysadmin to run this procedure without the job_id parameter.