Viewing 15 posts - 796 through 810 (of 59,063 total)
The problem is very likely that you're simply not doing any log file backups. Full backups do nothing to clear the log file.
If you want to be able to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2024 at 12:13 am
You need single quotes around the data that you're passing for @tempdata. I've added them in Red... one before the starting bracket and one after the ending bracket. Otherwise, your...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2024 at 11:52 pm
The method that both Ken and Phil are using is an arcane method known as a CROSSTAB and is a much more flexible manifestation than a PIVOT.
You can read more...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2024 at 11:39 pm
Another name for "conditional aggregation" is a CROSSTAB. MS use to carry a full entry in BOL on it until they came out with PIVOT. You'll be able to tell...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2024 at 11:30 pm
Publish well written standards, Enforce them. Period.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2024 at 5:06 am
I leave it at FULL because my database backups will try to do log file backups on any database not in the SIMPLE recovery model. That proc is also setup...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2024 at 6:46 pm
Honestly not fussed on the harshness of response if it contributes to moving the discussion forward - obviously meant in good humour.
It does sound like there are different opinions...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 5:59 pm
I also put something like that together where it would look like this
where ([definition] like '%INTO [tableName]%' or ([definition] like '%update [tableName]%')
That got me the closest...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 5:51 pm
Jeff Moden wrote:The real key here is... are people going to carry you down the hall on their shoulders if you make any changes here?
In a coffin?
A bit harsh!
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 4:09 pm
It also sounds like a possible "connection leak" in the applications that are hitting the database.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 4:01 pm
Unfortunately, I don't have a say about the structure of the table. It's populated via an ETL process. I just want to create dummy data for testing so want...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 3:59 pm
You could just search the "definition" column of sys.sql_modules for the table name with the understanding that it won't find ad hoc queries.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 3:54 pm
The real key here is... are people going to carry you down the hall on their shoulders if you make any changes here? If not, I'd leave it all be. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 23, 2024 at 3:20 pm
Well you can test that too.
My point is... the OP hasn't identified the scenario accurately enough to even try to determine which kind of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2024 at 4:57 am
You missed my point... and that's actually OK. I wasn't suggesting one of the other... I was pointing out that a whole lot of other people do and it's usually...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2024 at 4:52 am
Viewing 15 posts - 796 through 810 (of 59,063 total)