network profile
| bio | website | schoolofficepro.com |
|---|---|---|
| location | United States | |
| age | 39 | |
| visits | member for | 1 year, 11 months |
| seen | May 22 at 17:28 | |
| stats | profile views | 6 |
Owner of School Office Pro. We provide web based applications for schools to enable online registration, ecommerce, surveys, mass email broadcasting, job applications, and others.
|
Dec 10 |
comment |
SQL Server pivot query on Oracle source This worked. THanks |
|
Dec 10 |
accepted | SQL Server pivot query on Oracle source |
|
Dec 10 |
comment |
SQL Server pivot query on Oracle source BTW, I have to use the OPENQUERY syntax. The tables have oracle timestamps which prevent me from hitting them directly. The error code is ORA-00933 |
|
Dec 10 |
comment |
SQL Server pivot query on Oracle source When I tried to exec this across the linked server I get an error about sql command not properly terminated |
|
Dec 10 |
asked | SQL Server pivot query on Oracle source |
|
Sep 24 |
awarded | Commentator |
|
Sep 24 |
comment |
Select statement is locking a record I guess I'm confused as to why the row would be locked to begin with. The select goes first, then the update. Also, even if it was locking against writes, why the delay? The first transaction is purely a select. So I would expect any locks obtained to be released when the transaction is done. |
|
Sep 24 |
asked | Select statement is locking a record |
|
Aug 28 |
comment |
“lock request time out period exceeded” Error When Trying to See DB Hierarchies Based on your comment to my answer below, I think you need to provide a lot more information. How is the server sized, have you watched it's performance counters, is it swapping to disk or otherwise resource starved in some way. Be sure to actually check the above and not just assume anything. Further, does this happen when you connect while remoted into the desktop? Is the problem only occuring when accessing from a single location? What is the network weather like for that server (and your connection to it)? |
|
Aug 28 |
comment |
“lock request time out period exceeded” Error When Trying to See DB Hierarchies @LloydBanks: That doesn't mean this isn't a hardware problem. If I have 2 databases, one that's 20GB in size with a high transaction rate and another that's 1GB with a lower transaction rate then I'd expect the 1GB db to be swapped to virtual memory; which would increase query times. If the 20GB db was being hit hard enough, this could lead to connectivity issues with the smaller one. |
|
Aug 28 |
answered | “lock request time out period exceeded” Error When Trying to See DB Hierarchies |
|
Jun 30 |
awarded | Yearling |
|
Jun 8 |
awarded | Constituent |
|
Jun 8 |
awarded | Caucus |
|
Mar 3 |
awarded | Nice Answer |
|
Jan 27 |
comment |
securely exposing sql server 2008 for windows authentication A web app is typically better for the simple reason that if they do get in, they are limited to perform only the actions you allow them to. Whereas going straight to a database you have to be a lot more controlling on how you setup security.. which most people don't know how to do. |
|
Jan 27 |
comment |
securely exposing sql server 2008 for windows authentication The exact method of connection that your clients would use is immaterial. Just because you speak to the database using an ODBC connection doesn't mean someone else will. Also, from the database servers point of view it doesn't care if the client used ODBC, .Net providers, or even got down to the bare metal by hand constructing the tcp packets. The problem isn't how the Client connects, the problem is purely limiting who can even see the machine to begin with. |
|
Jan 27 |
comment |
securely exposing sql server 2008 for windows authentication SSL only encrypts the connection between the client and the server. It makes no representation that the client is in fact allowed to connect to your server at all. Regarding websites, people basically pray that the authentication mechanism is good enough to prevent brute force attacks. However, with database servers people rarely turn on the feature to audit account logins and even when they do they rarely bother reading the logs until after a problem has occurred. Even if you read the logs, you'll just spend days trying to block most of the internet from getting to it. Trust me: VPN. |
|
Jan 27 |
comment |
securely exposing sql server 2008 for windows authentication No. Again, bad idea. Port scanners will locate the server then you'll have a fairly large number of scripts attacking that machine day and night. Never mind the fact that worms like SQL Slammer spread because companies engaged in this practice. |
|
Jan 27 |
answered | securely exposing sql server 2008 for windows authentication |
