Viewing 15 posts - 54,346 through 54,360 (of 59,072 total)
The system has to be able to see the file to load it... make sure SQL Server Services use a startup account that can see the path to the file.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:39 pm
Heh... did you convert the correct column? Only way you can get that error is if the target column is actually an INT... double check the schema and make...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:24 pm
I think you would be unhappy... unless there's a pot wad of extra money involved... in which case, you'll still be unhappy but more satisfied 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:22 pm
What are you using to determine the size of the table?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:19 pm
No... I'd think not. What kind of "fields" are you talking about? Parameters from some GUI or columns in a table? Why wouldn't you know that max...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:17 pm
This looks like homework... I'd recommend that you post what you've tried so we can help you learn...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:14 pm
SQL Server also has Global Temp tables (##) which are a bit different than regular (#) temp tables.
The real key, though, is that you may be doing something wrong in...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:09 pm
My rule of thumb is to open it up... see how big it get's between backups... and then make it's initial size twice that big to handle "contingencies". Other...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:04 pm
Hi Tod,
I think you're headed down the right path... you haven't said anything (yet) that I don't think can be done in T-SQL. Your re-evaluation of the situation sounds...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:00 pm
Ok... 3rd time I've asked... If you let us know what the CLR is supposed to do, we can tell you if it can be done in T-SQL and maybe...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 9:00 am
You bet... thanks for the feedback, Eric.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:57 am
Ah crud... my bad... I gotta learn to read which forum these are in... I know squat about reporting services... my appologies.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:55 am
Ah... just a note... if the concatenation exceeds 8000 characters in SQL Server 2000, there's virtually no chance of displaying the full width of the concatenation and we may have...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:50 am
... If the max number of Sequences is not known... we can convert this to something a bit more dynamic...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:45 am
emamet (11/2/2007)
Guys,Yes, it is 2k5 specific.
Yes it is a correlated sub query but why is this a problem?
Typically, yes... correlated subqueries tend to be slower than a nice derived table...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:43 am
Viewing 15 posts - 54,346 through 54,360 (of 59,072 total)