Viewing 15 posts - 121 through 135 (of 919 total)
This error usually happens when the account the SQL Server is running under does not have permission to the drive/directory/file being mentioned. Check the account's permissions and make sure the...
April 24, 2013 at 2:34 pm
That expansion doesn't sound unreasonable, given the type of alteration you are doing, particularly if the columns you were altering made up the lion's share of the row size. ...
April 24, 2013 at 12:12 pm
What was the original file size? if it was 85 and the system had to take 2 expansions along the way, the last 10 it grabbed might have pushed...
April 16, 2013 at 3:03 pm
What is the growth increment for the file (if it's auto-grow). Could be that the multiples of the growth increment onto the original size forced the last expansion to...
April 16, 2013 at 2:54 pm
You might have better luck with these questions if you click the 'join the discussion' link at the end of the article. The authors may or may not be...
April 15, 2013 at 1:39 pm
If you are dealing with accounting periods that don't map to the calendar, I don't know of any good way to do this other than constructing a calendar table with...
April 15, 2013 at 11:53 am
What is the actual error message and where in the process does it happen?
April 2, 2013 at 4:50 pm
Usual cause is that the account under which the sql server is running does not have access rights to that file or directory.
April 2, 2013 at 1:14 pm
Something like:
select key, segment, max(value) from whatevertheheckyourtablenameis
group by key,segment
order by key,segment
April 1, 2013 at 3:38 pm
That sounds right, as long as the permissions to the share were set up correctly for the account running the .bat file. Did you try it?
March 29, 2013 at 3:46 pm
The cursor has been defined in one of the previous executions and never got closed and deallocated. Issue the close and deallocate commands by themselves or just get a...
March 29, 2013 at 11:33 am
Remove the 'GO'. That breaks the script up into 2 separately executable pieces and you need this to be one execution stream.
Also, is there a specific reason to use...
March 29, 2013 at 11:23 am
The command file you pass into SQLCMD should not be the stored proc, it should just be the command to execute the proc:
USE databasename
GO
EXEC storedprocname
GO
Since the proc already exists in...
March 29, 2013 at 11:18 am
Lynn's suggested solution using OUTPUT is superior to the one I gave you. Use his.
March 25, 2013 at 3:23 pm
Once you get the indexes correctly applied, would'n it be better to:
begin
Update the number by 1 -- this should establish the lock and keep anyone from reading it
get...
March 25, 2013 at 3:20 pm
Viewing 15 posts - 121 through 135 (of 919 total)