Viewing 15 posts - 46 through 60 (of 63 total)
OK, given that you are doing everything in dev, you're cool.
Question: In your "Destructive" method you list the step:
"Using same prod db, Select into temp, drop existing table,...
January 24, 2005 at 9:42 am
Well, FWIW, I don't like your "Destructive Method" because you are creating your test tables in the Production database(s).
The "Pull Method" is better, but you still are using the...
January 24, 2005 at 9:28 am
Actually, along with Merge Replication (which is more compliated because it requires conflict resolution rules to be established), there are special options called "Immediate Updating" and "Queued Updating" which allow data...
January 24, 2005 at 9:10 am
(Try running the samples again--I edited my last post)
January 20, 2005 at 8:01 am
Not real sure what you want to do, but check out these commands (from BOL). Perhaps they'll give you some of what you're looking for!
SELECT SYSTEM_USER
GO
SELECT HOST_NAME()
GO
SELECT USER_NAME()
GO
January 20, 2005 at 7:46 am
Personally, I think it's a great idea to include the block around the stored procedure.
Why? Well, as future versions of SQL come out and the lines between Transact-SQL and pure CLR code begin...
January 19, 2005 at 1:04 pm
Well,
You've got to expect some arithmetic roundoff to occur. Numbers you're getting don't seem that unreasonable. That's the way the numerical cookie crumbles.
One suggestion, though. To reduce the effects of ...
January 14, 2005 at 7:35 am
Well, I know very little about Reporting Server, but could your query be written with the "CHAR()" operator? For example:
Instead of:
SELECT 'This is a string with a # symbol'
Replace with something...
September 14, 2004 at 8:44 am
Another approach which will ONLY be practical if the maximum value of [X] is small and your query is relatively short:
Use a case statement with MAX(X) or MAX(X + 1)...
September 1, 2004 at 1:09 pm
(Update--continued from last post) Actually, I vaguely recall having "gotten burned" by some weird NULL-handling behavior in a query like this. Things didn't always perform as expected.
Instead of testing against...
August 24, 2004 at 10:43 am
This SEEMS to work, but no guarantees!
- john
USE Northwind
GO
-- Demonstrate A Query Using An Optional Parameter
CREATE PROCEDURE spGetOrders
@OrderID INT = NULL
AS
BEGIN
SELECT OrderID,...
August 24, 2004 at 10:17 am
Well,
I don't have an answer(!) But you've got several variables here, and you might investigate this phenomenon further by exploring individual scenarios one-at-a-time (at least that's how I'd try to attack the problem). For example, investigate:
(1) The number of...
August 24, 2004 at 9:09 am
Well, sounds like there's going to be a lot of administration work in any scenario...
Have you considered multiple environments?
In our env. we have a "development" instance where developers can...
July 28, 2004 at 5:34 pm
>>this won't let them modify the SPs though - only execute
Hey yeah, you're right -- sorry I didn't see in the original message that they wanted to be able...
July 27, 2004 at 5:13 pm
Viewing 15 posts - 46 through 60 (of 63 total)