Viewing 15 posts - 571 through 585 (of 701 total)
The trick that's helped me the most: just book the test.
Once I start getting comfortable with what will be on the test - but long before I'm ready - I'll register for...
June 27, 2006 at 12:06 am
Jeff: CREATE and DROP prohibit use of the database name. They must be executed in the context of the target database.
-Eddie
June 26, 2006 at 11:23 pm
If you wish to cascade some of the time, based on the situation, then it sounds more like a business rule than a data integrity rule. Business logic should be...
June 26, 2006 at 3:04 pm
Be sure to fire a USE statement first, then the database context is set:
USE
MyDB
GO
SET
ANSI_NULLS,
June 26, 2006 at 9:22 am
Every object has a four-part name: Server.Database.Owner.ObjectName
SQL Server will fill in the blanks with the current context if you leave any of them off. If I'm logged in to
June 26, 2006 at 7:20 am
It's hard to fight raw data, your plan of comparing reads and usage should be enough. If that doesn't make sense to the developers, then they are clearly stating that...
June 23, 2006 at 11:49 am
Just riding Ryan's solution, here.
To get yymmdd use 12 in the convert function, and 112 to get yyyymmdd:
SELECT convert(varchar, DATEADD(ss, @i, '01-01-1970'), 112) as 'My date yyyy'
June 23, 2006 at 10:48 am
What you describe can be done, but (and it's a little late I guess) structured naming solves a lot of the problem up front, grouping procedures by logical area, using...
June 23, 2006 at 10:41 am
>> 1. Is there a pattern to the ID list, or is it just a random blast of IDs?
> Random.
Shoot. Well, there goes that idea...
> Are there any obvious...
June 22, 2006 at 1:54 pm
The primary reason to send a recordset from a client to the server is if the client has modified the recordset.
In your case, it appears you're performing additional queries against...
June 21, 2006 at 1:32 pm
You can never be too rich, too thin, or have too much free data and log space.
June 21, 2006 at 10:34 am
If you get rid of the GROUP BY, you must also get rid of the SUM() (This is if you plan on using the detail in your report. Otherwise, leave...
June 21, 2006 at 10:29 am
That COMPUTE BY clause splits your results up into lots of tiny, independant resultsets, each divided by an additional independant resultset with your COMPUTE BY results for the preceeding data resultset. ...
June 20, 2006 at 11:00 pm
1. Is there a pattern to the ID list, or is it just a random blast of IDs? If there's some method to the ID madness, then there should be...
June 20, 2006 at 10:34 pm
Which edition of SQL Server 2005?
Enterprise and Developer Editions are good to 50 named instances per server.
-Eddie
June 20, 2006 at 10:03 pm
Viewing 15 posts - 571 through 585 (of 701 total)