Viewing 15 posts - 1 through 15 (of 698 total)
Through SQL? No. It's a command line driven process. Powershell is how I would do it. Check out DBATools.
As a bit of a sidebar, it's a real...
May 5, 2023 at 3:17 pm
Yeah - I probably could have simplified the question to just "why do aggregate functions return NULL instead of no rows" ... but now that I think about it, my...
March 1, 2023 at 7:09 pm
So this is a super-old thread to bump, but ironically, I'm working on SSIS packages again after several years, and this exact problem has been coming up again.
I realise now...
May 4, 2021 at 3:49 pm
That is some very useful info Brian - thanks! The setup I'm trying to create is indeed very similar to yours. Unfortunately since the system is a bit of a...
February 24, 2021 at 10:59 pm
@desnorton - I don't think sp_ExecuteSQL would actually diminish the danger. If the @WeatherFieldName variable had a semicolon in it, followed by a query - I believe it...
January 28, 2021 at 4:38 pm
@desnorton - yeah that does seem like it should work better. Still will look rather ugly when dealing with hundreds of columns though.
@scottpletcher - I'll take...
January 28, 2021 at 2:08 pm
The tables and fields are purely for demonstration purposes. The actual table definitions and field names are a bit more sensible (though not much more so).
As for your proposed solution...
January 27, 2021 at 9:27 pm
Short answer? 'Cause that's the way the third-party designed their schema / software :/
The #FieldValues table has a whole pile of columns (String_00, String_01, String_02, etc...), while the #FieldDefinitions table...
January 21, 2021 at 9:03 pm
Indeed. Sadly, I have no control over this. We're using a third-party application, and I'm retrofitting functionality onto it.
On the plus side, this is purely for auditing, so there shouldn't...
January 21, 2021 at 5:50 pm
Alright. Good news. Using the aforementioned approach, I was able to identify the problematic records. Unfortunately, I wasn't able to manually update or delete those records, but after running CHECKTABLE...
January 5, 2021 at 8:14 pm
Oh! I might have found something!!
I was reading through the original output, and I noticed that at the end there are several records of the following nature:
Msg 8929, Level 16,...
January 5, 2021 at 5:41 pm
So I did a bit more digging - running DBCC PAGE('mytable', 1, 101273, 2) WITH TABLERESULTS works, and produces the DATA output rows, but since it's a VARBINARY column, I...
January 5, 2021 at 5:01 pm
Will try the page check option and see if that gets me any more info.
Regarding restoring from a previous backup - to clarify, I do have a working...
January 5, 2021 at 3:32 pm
Ah. Roger. Will take a look and report back. Thanks!
January 5, 2021 at 3:32 pm
Hey Numpty,
The output I had pasted is the result of DBCC PAGE against that page. I'm not sure how to interpret that output though; is there something in there which...
January 5, 2021 at 3:12 pm
Viewing 15 posts - 1 through 15 (of 698 total)