we apparently don't need to worry about that here since we practically never apply any updates. Got tons of servers still running on SQL Server 2000. :-(
I've only been here for a few months, so I'm not quite certain. We have 125 instances or so, and I'm damn sure none of them have anything like the latest service pack.
at my last position, I had problems getting the query processor to take advantage of filtered indexes. Never could narrow down why it wouldn't use the filtered index, and instead would use a duplicate non-filtered index.
Alright Heap, i need your best sarcasm/snarkiness...
I'm doing a phone interview with a BI architect and he keeps saying something to the effect of "Guys, I have years and years of experience so I'm not sure why you are asking me these questions.""
I'm enjoying it. So far, I haven't had much exposure to the Sybase side, but this weekend I'm on call, so I'm pretty sure I'm being thrown into the deep-end.
@mmarie "in your years and years of experience, surely you've come across charlatans, idiots and assorted unemployables. These questions are designed to weed them out"
@mmarie "the questions are not designed for you, but for usual reporting monkeys. You'll best'em all with A+ and will make my boss put your CV to the higher end of the $ interval in our team."
As the other consultant constantly exclaimed "I should never be out of work" after solving the Nth problem that was found under the first bingle search result
I created views from two tables. When I delete all data in all tables, view keeps data as tables still have values.
What is all about?
EDIT:
I don't know types of view, so I will say it like this:
I created views as:
CREATE VIEW xxx
AS
SELECT columns
FROM table1, table2
WHERE co...
I had the same issue with SQL Server 2008. Dropping and recreating the view solved my problem at the time, but never got to go deeper. Hope something comes up in the answers. — Alireza38 mins ago
i'm using Attunity connectors for SSIS and keeps giving me an error "ORACLE registry key cannot be opened. Verify that the Oracle Client for Windows x86 is installed properly."
just i have the client installed
i guess maybe it could be installed in teh wrong place?
we're trying to put together a list of questions for her. we have a "factless fact" table which is essentially a collection of relationships that was used to bandage a design flaw. trying to figure out what to axe her
No, no, no. The purpose of a data warehouse is to keep SAN admins, DBAs, data modelers and developers employed. The business users are too dumb to use the beautiful things we deliver
@mmarie does that sound like a correct usage of a factless fact? seems dumb to me
i get the purpose of a factless fact, but if you're going to want to evaluate fund performance, why would you go through a factless fact to get to your fund fact instead of just having your dimensions in your fund fact??? sucks. oh well.
You can use either COPY FROM VERTICA or EXPORT TO VERTICA to import/export the data to another Vertica database. Both methods allow for data migration from a version that's an earlier release from the last major release (running 6.x, you can import from 5.x).
In the example below, I'll use EXPOR...