Sunday, March 11, 2012
CAL Question
different SQL Server databases (two to 1 and 1 to the
other) , yeah! looks funny, I know.
How many SQL Server CAL's do I need? Are these server CALs
or Device CALs or does it matter?
If I am using all three programs at the same time does it
make a difference? I would appreciate any input or even
clarifications on my question.
Ta!
A CAL (user or device, there is no such thing as a server CAL) allows you to
access any SQL Servers in your organisation. You still need licenses for
every server on which you install SQL Server of course.
Jacco Schalkwijk
SQL Server MVP
"dr. Fil" <anonymous@.discussions.microsoft.com> wrote in message
news:6cf401c475c9$5a3ed500$a601280a@.phx.gbl...
> If I have 3 programs on my desktop that connect to two
> different SQL Server databases (two to 1 and 1 to the
> other) , yeah! looks funny, I know.
> How many SQL Server CAL's do I need? Are these server CALs
> or Device CALs or does it matter?
> If I am using all three programs at the same time does it
> make a difference? I would appreciate any input or even
> clarifications on my question.
> Ta!
Thursday, March 8, 2012
Caching ForeignKey Collections & StoredProcedure Collections
I have a code generator for sql server databases, and I want to switch it over to using SMO instead of my custom built queries, but it's just painfully slow right now. With my custom stuff, I get complete generation in about 5 seconds, with SMO, it runs in about 12 minutes ( I got this down from about 45 minutes on the first run by setting my defaultinitfields to everything, and prefetching everything).
90% of the time is taken up in looking up the parameters for storedprocedures, as well as looking at the foreign keys of a table.
You can't set defaultinitfields on collections ( at least not that I can figure out), so what can I do?
Come on guys, this is supposedly a professional product. It's been almost two weeks and not a single developer has cared to provide a response?
And no, this isn't a bump, it's someone that's trying to get work done with something that looks to be completely inadequate, and hasn't received a bit of attention.
-- Colin