Viewing 15 posts - 826 through 840 (of 956 total)
If you look under the stored procedures, you should see a stored procedure with the name you used to define it inside the C# or VB.NET code. From SQL...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 29, 2008 at 7:22 pm
Can you describe what you have done so far so that we can better answer your question? Have you deployed the Assembly to SQL Server from VS 2005 using...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 29, 2008 at 2:56 pm
If all you want to know is how many times an update was run, and you don't care specifically which row(s) were affected then that would meet your need just...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 29, 2008 at 7:05 am
I don't understand what you are asking in your last question. Can you provide an example of what you are thinking?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 28, 2008 at 9:51 am
If the assembly can be cataloged with SAFE CAS rights, then I don't really see that there would be an issue with most DBA's that have read up on SQLCLR....
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 28, 2008 at 6:41 am
Thanks Gail,
You are correct, and I learned something I didn't previously know. 1204 and 1222 are the pertinent Trace Flags for the analysis of the deadlocking, and they both...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 27, 2008 at 7:38 am
One option would be to accept the date parameter as a string and then do a string.replace() to strip out the invalid characters. I don't know VB, but the...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 27, 2008 at 6:55 am
GilaMonster (10/27/2008)
r.dragoi (10/23/2008)
p.s. traceflag 3605 is not required. 1204 and 1205 or 1222 will do the job just fine.
Trace Flag 3605 with -1 will write the output of the other...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 27, 2008 at 5:34 am
I certainly can, and will. Give me until tomorrow, or perhaps the next day to provide an example of what I am talking about, and maybe find the right...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 26, 2008 at 8:39 pm
rbarryyoung (10/26/2008)
Actually, I see this as a fairly interesting proposal, particularly as a path-forward starting point for allowing some kind of dynamic querying while preventing injection threats.
LINQ already allows dynamic...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 26, 2008 at 7:15 pm
umanpowered (10/23/2008)
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 23, 2008 at 7:24 am
There is a script on this article:
http://www.sqlservercentral.com/articles/Administering/usingvbscripttoautomatetasks/1171/
I use a Operating System (CmdExec) step to call the script. If you save the script as DeleteOldBackups.vbs, then the Command for the...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 22, 2008 at 3:41 pm
Specific to your exact stored procedure it would be changing:
...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 22, 2008 at 1:02 pm
You need to double quote your filepath\filename if it contains spaces:
DEL "M:\Microsoft SQL Server\MSSQL.6\MSSQL\Backup\Categories_10-21-2008.bak"
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 22, 2008 at 12:58 pm
Unless you have a datetime column on the table that holds the last updated date, you won't be able to. There is no internal mechanism that tracks it for...
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 22, 2008 at 12:56 pm
Viewing 15 posts - 826 through 840 (of 956 total)