Am I Thinking Right Or Is It A Bug?
Nov 10, 2000
Please read the following statements. I got my expected results when I use the 3rd statement. How come second statement is giving me junk results.
First statement is just opposite of second and third statement,I believe.
First
-----
select table1.column1 from table1,table2 where table1.column1 =
table2.column1
select table1.column1 from table1 where column1 in (select column1
from table2)
Both results are same here.
The result is all the common rows.
Second
------
select table1.column1 from table1,table2 where table.column1 <> table2.column1
Third
------
select table1.column1 from table1 where column1 not in (select column1 from table2)
The result is
View 1 Replies
Dec 2, 1999
I don't know what Microsoft was trying to accomplish when they redid the way SQL 7 handles indexing, but as far as I'm concerned they failed badly. They just broke SQL Server, IMHO.
As a developer, I do not want to have to study rocket science just to get my queries to run fast. In SQL 6.5, if I wanted quick response on a join query, all I needed was an index on the fields I was joining on, in the join table. It worked, didn't have to mess with Profilers and Index Tuning Wizards, just load and go.
Now in 7, I might as well not bother. It's going to do what it wants to do regardless. Even if I use the Query Index Analyzer, and let it create the index it recommends, it still doesn't work. I'm sitting here watching queries I used to be able to run in seconds take 15, 20 minutes and longer.
It's time for the average guy to stand up to Microsoft's increasingly heavy hand and tell them to let us make the decisions on how we want to use our tools. Since 1995, they've been on a downhill slide as far as I'm concerned. Each new updgrade of VB, SQL Server, etc. is buggier and more of a hassle to work with than each previous version.
Enough's enough.
John M.
View 1 Replies
View Related
Nov 1, 1999
Hi,
Our front-end GUI person changed the system date one month back to avoid the expiration of the Servelet Exec software. After rebooting the system, MSSQL refuses to come up and the errorlog has the following message: "The evaluation period has expired". The version we had was never an evaluation version!
What's making it think that and is there a way to correct the situation?
Any help/suggestions would be greatly appreciated.
Thanks in advance,
Nishi
View 1 Replies
View Related
Mar 14, 2007
Imagine opening SQL Server Management Studio (SSMS), drilling into adatabase, and seeing all objects with little lock symbols in front ofthem. That would be true SS integration.Maybe next version?I know about creating a project in SSMS and managing connections,queries, and misc there, but come on, that seems a far cry from what Ilong for.I searched for 3rd party tools and found SQLSourceSafe and Apex SQLTools. Does anyone have experience with those?-Tom.
View 2 Replies
View Related
Nov 28, 2007
Hi All,
I've just started at a new job that is a little bit of a step up from my old job. At my previous job I was responsible for 5 instances of SQL Server with about 30 databases. My new job has me (and a team of 3 other DBA's) responsible for 100+ instances. The backup schedule and process is a mess. I'm thinking about moving everything to Maintenance Plans (some 2000, some 2005). I've always scheduled individual jobs for each database previously and done index maintenance manually, but I'm kinda leaning toward Maintenance Plans just to simplify everything.
Anyone out there have any input on how and why they chose MP's over scheduling backups db by db? Or anyone out there choose not to use MP's for a particular reason? Input is greatly appreciated.
Manny
View 1 Replies
View Related