The best way would be to put it in another schema and manage the security on that schema, but I will operating under the assumption that you can't move it...

I have a question regarding this.

Recently, our team reinvestigated our maintenance plan. With the addition of a SAN, and the movement of our database files to the SAN, we...

My hobby has always been computer programming (since I was a kid). Personally, I prefer game programming, but database programming definitely keeps me interested. I do spent some...

I think time off would be the best bonus ever. It could even be unpaid, I wouldn't care. Time off work is just plain good for mental health....

You can ATTACH a .mdf file, but not restore from it. Attaching it will create the database in the state in which it was detached. (Google: sql server...

Great Lowell, I'm glad I could help. For my requirements, 4000 characters was more than enough. I'm glad you were able to manipulate it to meet your needs.

--J

Great. I'm glad I could help.

--J

iklektic (5/25/2010)

---

Extremely useful tool! Thank you!!

The complete code I have for this query so far is:

DECLARE @StartDate datetime, @EndDate datetime

SELECT @StartDate = DATEADD(MONTH, -6, GETDATE()), @EndDate = GETDATE()

SELECT MAX(Customer.CustomerID)...

You will also need to:

ALTER DATABASE <dbname>

SET TRUSTWORTHY ON

For the database you are deploying the assembly to.

That's definitely strange. Personally, I deployed mine from VS, but I've deployed CLRs manually before, and didn't have any such problem.

If I script out my function, it looks...

The CTE is part of the query, and always belongs at the beginning (no matter how big the query).

It is the logical equivilent of creating a table variable:

DECLARE @indaterange TABLE...

I'd argue that calling a VBS from the command line is much less manageable than using CLR. Calling VBS from the command line introduces points of failure that don't...

CTE stands for "Common table expression". It's the equivlent of creating a table variable and then using it in the following query, except it all happens in a single...

CONVERT 101 should work fine then.

SELECT CONVERT(VARCHAR,DATEADD(year, -1, dateadd(s,-1,dateadd(dd,datediff(dd,0,getdate()),0))),101)

Returns "05/24/2009". But, it returns it as a VARCHAR, not a datetime. You should not use a VARCHAR for date...

He nixed the solution or the entire project? Did he give a reason?

--J