|
In the select statement I did not include the "Where" clause by mistake. But these values are being filled in by the Where clause. Sorry.
|
|
|
|
|
No, that still doesn't make any sense.
holdorf wrote: how are the select statement return values assigned to the variables, properties, that are in the calling code?
holdorf wrote: But these values are being filled in by the Where clause.
Executing a SQL query will never automatically update the value of a C# variable.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I guess I am not making myself clear. This is working SQL code that update the C# variables from the query after it is called. What my job is to remove all of the SQL inject errors that exist from this working code.
|
|
|
|
|
No, what you have posted is working-but-vulnerable code which executes a query that includes the values of some C# variables in the results.
At no point does the code you've posted update the value of any C# variables.
Either you've forgotten to post that part of the code, or the code isn't doing what you think it's doing.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I had a datbase with MDF file size 7GB but LDF file size is now 202GB. its big issue with my server. whats the best solution?
i tried to shrink but nothing happend. i took backup of logs but issue is still persist.
|
|
|
|
|
What the recovery mode of your DB?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
How have you done the log backup?
(Remember that even full database backup will not truncate log if you are using full recovery mode...Only direct log backup will work here)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Dear I take full back of DB after that i take only logs backup then try to shrink the log file but failed to reduce the LDF size.
|
|
|
|
|
Can you share the commands you run?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I do with MS management studio.
|
|
|
|
|
OK. Explain how! (when you are using the Management Studio you have a 'Script' button at the top of the backup window. Pressing that button will give you the script Management Studio will run - copy that here!)
(I ask you this because these kind of things are working so probably you miss something and I try to figure out what)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Please see the generated script
USE [TEST_APP]
GO
DBCC SHRINKFILE (N'TEST_APP_Log' , 0, TRUNCATEONLY)
GO
I just want to truncate the logs.
|
|
|
|
|
TRUNCATE_ONLY option does not reorganize the file but try to free the empty block at the end of the log file...It is possible that without page-reorganization there is no actual space to free...
Instead of TRUNCATE_ONLY use tager_size...
DBCC SHRINKFILE('your-log-file', 200)
It will take much more time as SQL will try to reorganize pages inside the log file and drop them if marked properly by the backup process...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I just need some help to configure the DB as when i take bake up of LDF then DB must truncate the logs and LDF again in 2mb size. is it possible ?
i am doing the same exercise on another DB but on this i am failed.
|
|
|
|
|
Not with your model...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Can i change the model ? how ?
|
|
|
|
|
ALTER DATABASE [your-database-name] SET RECOVERY SIMPLE;
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
my issue is still with me. on recovery model simple nothing happend ... can you suggest me some more options??
|
|
|
|
|
After changing to simple try shrinking the log file
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
Are you using replication?
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
No i am not using replication
|
|
|
|
|
In which case all you need to read this article[^]
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Try running the following query:
SELECT
[name],
recovery_model_desc,
log_reuse_wait_desc
FROM
sys.databases
WHERE
[name] = 'YourDatabaseName'
Compare the value returned to the list on TechNet:
Factors That Can Delay Log Truncation[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
running this query, i come to know that log_reuse_wait_desc is REPLICATION.
what should i do next ?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
