[dba-VB] C# - Direct data manipulation

Shamil Salakhetdinov shamil at smsconsulting.spb.ru
Thu Dec 3 05:29:49 CST 2009

Hi John --

OK. Don't break it with implementation of other approaches if it works...

Just for the future projects - I suppose (I might be missing something as I
do not have that experience but I plan to try, maybe within our
Northwind.NET project) this partitioning stuff is just practical for the
tasks as you do (similar stuff was available for non-relational DBMSs in the
end of 70-es/beginning of 80ies, and for Oracle it's available for years now
AFAIHH), and this stuff doesn't take that much time to learn (one day?)  and
use (a few short reusable T-SQL scripts?) that it would  take to program and
to test and to support dynamic T-SQ: for many SPs and UDFs...

Thank you.


-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, December 02, 2009 10:32 PM
To: Discussion concerning Visual Basic and related programming issues.
Subject: Re: [dba-VB] C# - Direct data manipulation


I have not.

All of that is rather esoteric stuff for a non DBA.  My job is processing
data, and that is only a 
small part of my job, i.e. this is only one of many clients, and the only
one that needs this kind 
of SQL Server stuff.

As I have said many times, if my job was to go into a company every day and
play DBA then I would 
learn many more things SQL Server related.  As things stand I learn just
enough to make things work, 
and a LITTLE extra in search of efficiency.  It is certainly not that I
don't want to, I just don't 
have the time.

In the end I find the method I use comfortable from many angles.  I have to
do some things that 
require creating views, other "processing" tables and so forth.  It really
just works (for me) to do 
things this way, have separate databases to hold all of the "junk"
associated with each list.  Kind 
of the old "encapsulation" thing.

Your suggestion would of course end up with all tables inside of a single
"database", and as such 
the need for the Database parameter would go away but I still have to do the
same thing to many 
different tables.

Again, could this be done by one of the experts on the SQL Server list.
Probably!  Will I ever get 
there?  Uhhhh doubtful.

John W. Colby

<<< snip >>>

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4656 (20091202) __________

The message was checked by ESET NOD32 Antivirus.


More information about the dba-VB mailing list