Viewing 15 posts - 24,331 through 24,345 (of 59,099 total)
sqldriver (2/18/2014)
Jeff Moden (2/18/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 9:48 pm
MyDoggieJessie (2/18/2014)
What we can ALL AGREE upon is whichever route you take, please DO NOT SKIP STEP #10
Heh... I'll drink to that! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 9:37 pm
zulfansari (2/18/2014)
I'm sorry about the confusion, I guess I should take it step by step, first I need to add a total column as the last column so then...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 9:32 pm
SQLRNNR (2/18/2014)
How important is the data to your company/client? Do they have an RTO/RPO specified? In other words, what is the maximum allowable...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 3:14 pm
Post withdrawn. I thought this was going to turn out to be a massive double triangular join but a second look-see says it probably won't.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 3:04 pm
cygne17_2 77208 (2/18/2014)
I found a sql server database with a transaction log file of 65 GB.
The database is configured with the recovery model option = full.
Also, I noticed than since...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 2:53 pm
I guess I don't understand the need for any preprocessing here. Just load the each group of files into a working table (heaps, to be sure) and do your...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 2:44 pm
jiayi345 (2/18/2014)
Say I have 100 schemas all with the table "orders" is there an easy way to write one query to query them all?cust1.orders
cust2.orders
cust3.orders
cust4.orders
etc...
Yes... write a spot of dynamic SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 11:10 am
IIRC correctly, there was a bug that cause this behaviour depending on the INITIAL SIZE and GrOWTH SETTINGS of a database in SQL Server 2005. I believe that SP3...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 9:04 am
Steve Jones - SSC Editor (2/18/2014)
Jeff Moden (2/16/2014)
As I stated peviously, the OP is frequently the worst person to judge answers. You have to remember that they asked the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 8:47 am
tonyabrhm (2/18/2014)
I am trying to create a query which shows data from the past 1, 2, 3 4 and 5 years in seperate columns. I beleive I have the within...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 8:41 am
BrainDonor (2/18/2014)
mandir.jain (2/18/2014)
one scenario may benefit from creating ,other scenarios may not. So how to decide ? how many scenarios to test? 🙂
Indeed. And somebody has to make the decision...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 8:37 am
Once you have all of the problems resolved with the "non-existing parent" problem, you should add a self-referencing FK that contrains the values of parentIDs to only those values available...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 8:12 am
kalikoi (2/18/2014)
TableA
------
Col1 col2 col3
1 C01 1
2 C02 2
3 C03 1
4...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 6:52 am
My recommendation would be to see if the built in "Help" for Idera might save you some time. It's most likely that pressing the {f1} key while the tool...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 18, 2014 at 6:49 am
Viewing 15 posts - 24,331 through 24,345 (of 59,099 total)