Viewing 15 posts - 49,726 through 49,740 (of 59,091 total)
Juergen.Guenther (6/24/2008)
i have the same problem with Dell Latitude D830 - unfortunatly changing the video card is no option for my laptop 🙁
Disabling the hardware acceration worked - but is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 9:01 pm
jimige257 (6/24/2008)
Is it worth spending 2 hours optimizing a prodedure that works now and is needed last week? Many would say not.
And, THAT is why I tell folks that every...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 8:57 pm
Saroj (6/24/2008)
Authors Books
Pk Author ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:56 pm
balasach82 (6/12/2008)
exec xp_cmdshell 'copy C:\templates\BALAJI1.xls C:\export\BALAJI1.xls'
insert into OPENROWSET(
'Microsoft.Jet.OLEDB.4.0',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:43 pm
Did anyone ever find an answer on this? If not, does anyone know the answer for this?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:29 pm
The answer is "Yes"... both can be done. Create a view in SQL Server to look at the data you want and then create a spreadsheet to use "External...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:28 pm
So, Bob! Just curious... did Jack's code work or what?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:25 pm
Paul McKay (5/21/2008)
I'll stick up some data for this tomorrow following Jeff's guidelines if I can.
Is it tomorrow yet? 😉
Just teasing... did you ever get this figured out, Paul?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:19 pm
David O (5/7/2008)
I just spent an afternoon re-writing a proc that should have been easy to write but instead I get a piece of crap that kills my server.
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 7:15 pm
The code you have posted is not meant to be executed by you... things like sp_cursoropen are SQL Server code that appears when SQL Server actually runs a stored proc.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:51 pm
This old trick using a Tally table may help... I did not modify it to match your tables... see the link in my signature if you want that 😉
--===== This...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:46 pm
I don't know of a direct method... but can you have MySQL export to either a Tab Delimited or CSV file? From there, it's easy to import into SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:43 pm
Constraints are meant to protect the data.... little things like Primary Keys and Foreign keys as well as some data level constraints in columns keep people from entering garbage into...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:37 pm
Ummm... you're probably not getting any answers because there's not really enough data for folks to go on.... and a lot of them (me included) want to see some other...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:33 pm
If you can run it, then the job needs the same privs as you.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2008 at 6:01 pm
Viewing 15 posts - 49,726 through 49,740 (of 59,091 total)