You’re offline. This is a read only version of the page.
Announcements
Newbie here,
I am trying to find out why we sometimes have a bunch of reads from the syscolumns table
It looks like this:
Select CONVERT(CHAR(30),sc.name), sc.type, sc.usertype, sc.length, sc.status from syscolumns sc where sc.id = object_id( 'inventory_ext' )
There can be from a few to as many as 20 such statements in a bunch, all using a different table name (with object_id)
Does anyone know if that really is useful ? Any way to turn that off ?
Thanks
*This post is locked for comments
I understand what you are saying.
I am very disappointed to learn that, I expected the product to be better than that at accessing the database.
Thank you for your answer.
Yes, it is useful.
Dynamics SL has its own database layer, which is how the SL client talks to the database. For the SL client to understand what the datastream from the database means, the layer has to query the corresponding metadata, which resides in the syscolumns table. I've built some database layer in the past and that's the standard way to do it.
Turning this off would be like turning off your car engine. Maybe you can do it, but the car won't take you anywhere.
I guess this goes back to when SL was first ported to Visual Basic technology. There wasn't at the time a fast and reliable database connector for VB, so Solomon had to build one from scratch.
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
