Yuri55 (1/6/2013)

---

Thanks guys for all your answers-

just to summarize- for index maintenance we need to take into account both logical fragmentation and page density. Still have couple questions left:...

I am unable to recreate the scenario, i.e. I am able to delete from remote tables referenced by 4-part naming using an IN with a temp table to achieve a...

Security and risk mitigation have to be layered and the risk-to-benefit ratio for xp_cmdshell simply makes it a non-choice for me. I put SQLCLR objects with EXTERNAL_ACCESS and UNSAFE in...

Assuming you mean the allocation unit size defined when you format a Windows drive then it will depend on the workload but 64 KB is usually a good place to...

You can develop in and against production if you like but it is not recommend and typically will not bring you the best results in terms of releasing quality software...

Could you please script out your Linked Server definition and post it here minus any sensitive information? Also, which MySQL driver, type and version, are you using?

Jeff Moden (1/13/2013)

---

I think having the ability to audit is definitely the definitive reason to use CLR over xp_CmdShell. I think it's great that the user the hacker broke...

No...

Naturally. It, like sys.xp_cmdshell, is disabled by...

Jay Pete (1/7/2013)

---

Hi All,

I want to rename the file on the base of query output in SSIS.

Example:

File name: report.txt

Query: Select MAX(Batchlog) from Account -- Query Output is 100

So, file name...

SQL Server already keeps track of this in the SQL Error Log. SQL Server adds an entry to the Error Log whenever a server configuration option changes.

What are you trying...

One of the many advantages of using the SQLCLR over xp_cmdshell for interacting with the file system is that if the user connected to SQL Server under Windows Authentication you...

Jacob Pressures (1/9/2013)

---

The TVP seems, at least in my head, like an alternative method although It would probably still not allow for query optimization and would put a lot of...

I am assuming this was your post on MSDN and it is now resolved:

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/d00bb280-77bd-487c-8785-658beb08e296

Here is a tutorial on how you might be able to capture the number of affected rows into a variable, depending on how your SQL Statement in your Execute SQL...