Viewing 15 posts - 241 through 255 (of 275 total)
Sorry, I can't point you in the direction of any specific SOX documentation; the work I did was over 8 years ago at a different employer. We didn't go through...
July 23, 2014 at 1:43 am
I'd add one thing to Craig's post; SOX isn't just about data - you need the paper trail for code changes too (table/view definitions, stored procedures, functions, triggers, etc.).
Chris
July 22, 2014 at 7:45 am
John,
all our C# applications use stored procedures to change data; it's the easiest way to set up the security so that users can do only what you want them to...
July 10, 2014 at 8:15 am
+1 for Luis' post. The query results grid in SSMS was never intended as an end-user reporting tool; there are separate purpose-built tools for that. I use the SSMS grid...
July 3, 2014 at 7:56 am
I also put "Just B" on the basis that ordering by name in query C isn't guaranteed.
June 26, 2014 at 3:53 am
I was thinking of * in it's Unix/Windows context as meaning 'All' rather than 'Star'. You can thank Douglas Adams for my original answer.
I do know what it actually returns,...
June 20, 2014 at 3:35 am
Surely SELECT COUNT(*) should return 42?
June 20, 2014 at 2:45 am
We had SQL_Latin1_General_CP1_CI_AS on our 2005 server and most of the existing databases and were moving to Latin1_General_CI_AS on the 2008 server.
In Visual Studio, I used the option to generate...
May 29, 2014 at 1:58 am
Note: with Visual Studio 2013, you do get the SQL tools with the Professional version.
May 28, 2014 at 2:01 am
I have just completed a project with exactly the same issue you had. We decided to go for the rebuild/reimport data option to get the database collations the same as...
May 28, 2014 at 1:53 am
We use SSDT with Visual Studio 2013 and it works quite well; the ability to use TFS for source control is particularly useful along with generating the change scripts for...
May 27, 2014 at 1:46 am
I would also suggest you review the C# code slightly; it would be better to create the parameters explicitly with the datatypes used by the stored procedure, eg.
SqlParameter parm00 =...
May 22, 2014 at 2:43 am
I don't think AmandS was suggesting buggy code, bad design, etc. should become viewed as emergent practice. Just that new programming methods and features become available before standards can be...
May 16, 2014 at 9:50 am
From what I remember of SOX, the answer depends partly on the type of data in your database (and mostly on who is auditing your SOX compliance). If your development...
May 16, 2014 at 2:00 am
Viewing 15 posts - 241 through 255 (of 275 total)